-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please improve usability of UI with better searches and keyboard controls #79
Comments
Good list! BTW, a shortcut CTRL+G usually means GoTo Line in current window... cheers |
Thanks, @greenozon. Re 3, extra dialog might not be too much of a bother if closeable with "esc", since keys are on the keyboard already for the find operation, but it's ok not have it as long as there's visual indication nothing is found and I am not abruptly taken to the top of the file. Re 4, not exactly the same, F3 just does a find next but if it still wraps search, no good. Re 6, precisely, and it's used for approximately the same activities :) Re 7, I did not realize Ctrl-w did the same, I am so very used to Ctrl-f4 in browsers and eclipse. Can be lower priority if desired. |
1.. You may need to elaborate on this. Are you searching for a class name? |
Thanks for consideration!! :) |
Thanks!! |
Please make the UI of this (already very nice and helpful) tool even better by adding a few more more search options and :
Allow class-level search, by class name ("String"), full package/ class name ("java.lang.String") or package abbreviation ("j.l.String")
When UI first loads a file, please show a floating search bar at top of main screen; it would allow searches right away, kind of like the search bar at the top of github does.
If I do control-F and the tool does not find anything, please show "no matches found" and stay in place instead of jumping to the top of the screen.
By default, do not wrap searches. As is, I always have to keep an eye on the scrollbar to see if search just jumped to the top of the file (meaning there are no more results). It's OK to have a checkbox option for it, but please don't do it by default.
Allow global full search (yes, even if it might be quite slow), covering full text of all classes, property files, mf files, etc.
After control-clicking and jumping to a class/method reference, allow "escape" key to close that window and return to the original location.
Close current window / class view using Control-F4.
Thank you!
The text was updated successfully, but these errors were encountered: