Please tell how to turn on search input for "fix Version" jira ticket's field.
Now I have follow view mode for fix Version field without search input. Only long list:
But I would like following edit mode for fix Version field.
On both screens are different jira versions from different organization.
Question is about input for search by fix Versions. In first screen I can choose version from long scrollable list. I can't input prefix of version for fast choice. Work around is ctrl+F from browser but it is pain.
I would like UX for fix Version field like on second screen. But I don't know how turn on it.
I found solution - https://confluence.atlassian.com/adminjiraserver/configuring-renderers-938847270.html#Configuringrenderers-autocompleterenderer
We should set Autocomplete renderer for fix version field.
Related
I want to send the file I'm currently editing to a printer, like I did in Notepad++ for example.
I havn't found any hint on a print command. Is it not possible ?
It is not yet available, but I found an issue report for that feature.
It's currently in the backlog, so we can expect it soon.
https://github.com/Microsoft/vscode/issues/5953
Edit:
In the meantime:
https://marketplace.visualstudio.com/items?itemName=nobuhito.printcode
https://marketplace.visualstudio.com/items?itemName=pdconsec.vscode-print
Now you can install addon for VS Code - search "PrintCode".
Note that the repository for this extension was last updated in February 2018 with numerous issues outstanding.
I found the PrintCode extension inspiring but unfinished and with a number of flaws. In particular it depends on a specific paper size to wrap and as a result does not respond well if you change paper size or orientation in the print dialog.
It's open source so I looked at the code and didn't like that either. No programmer ever likes another's coding style. So I pinched the idea of using a web-browser as platform driver for HTML printing -- my hat is off to the PrintCode author for that cunning insight -- and wrote my own.
In the process I fixed all the known bugs, added everything on my wishlist and a couple of things suggested by others. The biggest thing was figuring out the CSS required to respect print dialog paper size and orientation. This also sorts out the mysterious disappearing line numbers problem, although I'm not sure why. The next biggest thing was learning to probe for an unused port, a problem that also afflicts PrintCode causing the browser to open showing no content.
Major issues
PrintCode depends on a web service. You can't use it offline.
Many people want to be able to open a file, select a portion and print just the selection.
The print dialog supports changing paper size and orientation. This clashes with the way PrintCode works.
Some people like to run multiple VS Code windows.
When you print a markdown file, you probably don't want it printed like a text file when it can be rendered with fonts and proper headings and bullets etc.
Support is required for remote workspaces.
Because each instance of VS Code needs a different port for its embedded webserver, you can't just use a setting. Dynamic port allocation is necessary.
Remote workspaces weren't even a thing until two years after maintenance ceased on PrintCode.
If you want to survey your options, get onto https://marketplace.visualstudio.com, choose the Visual Studio Code tab and search for printing.
If you just want a link to my version, it's here http://marketplace.visualstudio.com/items?itemName=pdconsec.vscode-print.
If you like what you see but need something I haven't thought of, the marketplace page has a link to the repo on github. Create an issue and tell me what you need -- or write it yourself and submit a PR.
Now there is an extension available for printing from the VS Code Editor.
It's called VS Code Printing Free.
I've tried it for a couple of days and it works fine.
Poor man's answer: Copy code to Notepad2 or Notepad++ and print from there.
The colour coding will be different though
You can use an Extension of VS Code: PrintCode
Install extension PrintCode
On Mac: command + shift + P
choose command> PrintCode
I have modified the https://marketplace.visualstudio.com/items?itemName=pdconsec.vscode-print. If you change the values that I have marked in the picture in the extension settings a browser tab opens with the you can then print this also works on the Ipad. It works also with the code-server Version inside a Docker Container.
I put the file on github https://github.com/chrishdx/vsc-print
enter image description here
I have tried changing the background color of toolbar in notepad++. I am not been successful so far. Frankly speaking I am not so liking the toolbar color and would like to have a dark background to the toolbar. Is there anyway I can do the same? Thanks in advance
Take a look at this question on Superuser. I haven't tested it, but I think it can help.
below there's the hack (as explained in the link):
The themes, as you guessed, can't do this (they only handle what's in
the text editing window). To change the colors you'll have to make
some very simple changes (since it's only changing color values) to
the source code (download from the site or GitHub).
Extract the file Find the elements whose color you'd like to change,
and change them. All colors I've seen are denoted RGB(xx,xx,xx)
Rebuild (see /readmeFirst.txt once you've extracted) I've just glanced
at these files, but I'm definitely going to work at this a little
tomorrow and I don't mind giving you my results once I've solved it.
Anyway, what I've seen at a glance is that you'll want to look in
/PowerEditor/src/ScitillaComponent/DocTabView (I think)
/PowerEditor/src/WinControls/TabBar
/PowerEditor/src/WinControls/ToolBar That's all I noticed that might
be of interest so far, but again, I'll look at it more tomorrow and
get back to you.
Edit: the official makefile will give some errors, because
/PowerEditor/src/Parameters.h references files incorrectly. Here are
the two I fixed so far:
#include "TinyXml/tinyXmlA/tinyxmlA.h" (line 33)
#include "TinyXml/tinyxml.h" (line 37)
Change those lines in Parameters.h to what I've written to deal with
them. Don't worry about the warnings ("extra tokens after #endif") -
they're just comments.
Edit 2: I'm using VS2012, in which the build process results in
numerous errors. I won't post them here unless someone eventually asks
about them, in which case I'm happy to do so. I should have a working
build up soon!
Edit 3: It seems Notepad++'s provided VS project file was created with
an earlier version of Visual Studio, and in updating the files, Visual
Studio 2012 creates many problems, so if you go that route, use
VS2010.
Edit 4: I didn't make it obvious in Edit 3, but I gave up after
realizing just how difficult it was going to be to get around the VS
errors. I imagine the code has changed significantly since I wrote
this answer as well; unfortunately I didn't note the version, but I'm
sure it was the latest available at time of writing this answer,
which, according to "All versions", was probably either 6.4.1 or
6.4.2. However, I hope this is a useful starting point for anyone else who reads (this answer has received consistent attention since
writing).
As far as I see into details of creation of the user interface elements (buttons, toolbars etc.), the answer is that toolbar color cannot be changed until developer explicitly built such a feature into the application. And N++ has no such a feature if you check its settings.
You can achieve changing of toolbar color by standard way: override toolbar painting routine after you grabbed N++ sources. Then compile custom Notepad++.exe which reflects your change.
If you feel toolbar coloring would be useful not only for you, but for number of users, consider registering a feature request for Notepad++ as many people (including me :)) already did for various features of N++.
Go to Settings> Preferences
Then select Enable dark mode.
Then you have the option to pick colors for the dark mode and can even set custom colors
Simple question, (Easy points!)
In Delphi 2010 (with updates 4 and 5) "Find in Files" shows the results with the tree closed for each file. I have to click on a plus-sign to open each file's results.
I know there's a way to configure the IDE to automatically show the results with all the trees open, but for some reason (fatigue on my part?) I'm unable to find where to set that option.
Tom
Edit on year later: I re-asked this question here: Auto-expanding the results of "Find in Files" int the Messages windows and got a good answer:
"[Use the] Group results by file" checkbox on the Find In Files dialog.
Somehow I'd overlooked that! I'm posting this edit so that other readers in the future find it here.
I couldn't find anything like what you are asking about, in the Options. Perhaps you confused that with something else, but maybe I overlooked the option (too).
Anyway, there's a keyboard shortcut, Ctrl+Shift+Numpad +, to automatically expand all the tree items in the Message box tree view (when it is focused). Similarly, Ctrl+Shift+Numpad - collapses them all.
Not directly answering your question; but I was often frustrated by this, until I found the excellent Grep Search that is included with GExperts
It includes an option to 'Expand all matches after searching'. It also fixes many other shortcomings with the Delphi 'Find in Files'. I highly recommend it.
In Delphi 7 when i ran multiple Find In Files searches each search result would generate a separate tab. We've since upgraded to Delphi 2010 and now when i run multiple Find In Files searches each time one is fired off it replaces the tab instead of creating a new one with the results of the successive search. Is there a way to get the old functionality back, a setting somewhere?
Thank you,
Brian
In the Find in Files dialog, there is an option "Display results in separate tab". Make sure that is checked, and the behavior should be what you want.
You can look into using a vertical grid for that. DevExpress' VerticalGrid can duplicate that functionality.
Has anyone used wmd editor?
I am having a problem with the editor in a form. Its not being configured as the editor after setting up in a form. Only the text area is shown with no editing options. The form has already many controls and other scripting files included. I am using IE 7. Its working in another form which has only a text area in it.
Is this due to any conflict with other scripting files or any other issue?
I have used WMD (over here), though I don't know that it's really relevant; without a lot more detail, the advice I can give you is pretty general.
That being: yes, it probably is a conflict with some other element you're pulling into your form, and I recommend that you test this by commenting out everything but the WMD support, seeing if it works, and if it does, then re-adding things one at a time until you find one that breaks it. Then see if you can resolve the conflict in some way.