The Function works fine if called from the menu but no combination of key-presses works (I've tried [Alt]/[Ctrl]/[Win], all with/without [SHIFT]) - the same applies to meta+O, meta+R, meta+W.
Simon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the report. I changed it now so that you can use either CTRL+<somekey> or META+<somekey>. Can you try again from the latest source and let me know if that works for you ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just got ANT on my system for the first time and tried r124 (as expected: doesn't work) and r125 (as expected: [Ctrl] worked fine). It just looks kind of weird because [Meta] is set as first accelerator and therefore is shown in the menu (this could really confuse windows users...).
Not sure if a rewrite of setAccelerators() doing item.setAccelerator on the first keyStrokeDefintion depending on System.getProperty("os.name") would be useful (skip meta depending on "Windows").
Simon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You're right that the discrepancy between the menus and the actual accelerators might be confusing. So another attempt at this in r127: I now set it up as "meta <key>" on Mac OS X, "ctrl <key>" on others. So it's platform dependent, with using CTRL as the default on everything except Mac. This way there is only one way of doing it on each platform, and no more mismatch between what the menus say and what the user should type.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The search function in r158 has two issues:
- The positioning is not correct (I'd expect it to position [and mark/highlight]) the stuff that was to be find)
- As COBOL words are not case-sensitive the find function shouldn't default to or even be case-sensitive neither [while a checkbox "case-sensitive" in find dialogue would be nice]
We can close this ticket after these two are done (and add another low-priority one for Regex ;-)
Simon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
r120: Added "go to line" to the GUI. Shortcut is "meta+L" (should be "ctrl+L on Windows).
The Function works fine if called from the menu but no combination of key-presses works (I've tried [Alt]/[Ctrl]/[Win], all with/without [SHIFT]) - the same applies to meta+O, meta+R, meta+W.
Simon
Thanks for the report. I changed it now so that you can use either CTRL+<somekey> or META+<somekey>. Can you try again from the latest source and let me know if that works for you ?
Just got ANT on my system for the first time and tried r124 (as expected: doesn't work) and r125 (as expected: [Ctrl] worked fine). It just looks kind of weird because [Meta] is set as first accelerator and therefore is shown in the menu (this could really confuse windows users...).
Not sure if a rewrite of setAccelerators() doing item.setAccelerator on the first keyStrokeDefintion depending on System.getProperty("os.name") would be useful (skip meta depending on "Windows").
Simon
You're right that the discrepancy between the menus and the actual accelerators might be confusing. So another attempt at this in r127: I now set it up as "meta <key>" on Mac OS X, "ctrl <key>" on others. So it's platform dependent, with using CTRL as the default on everything except Mac. This way there is only one way of doing it on each platform, and no more mismatch between what the menus say and what the user should type.
Works fine now. You may want to support other mac versions, too, by changing
- if ("Mac OS X".equals(os)) + if (os.toUpperCase().indexOf("MAC") == 0)Just an idea, not a request.
Simon
Basic search functionality has been added in [r158]. Check the changelog for the details.
Simon, please let me know if this makes for an acceptable implementation of the search functionality. If so, feel free to close this issue.
Related
Commit: [r158]
Last edit: KrisDS 2013-09-11
The search function in r158 has two issues:
- The positioning is not correct (I'd expect it to position [and mark/highlight]) the stuff that was to be find)
- As COBOL words are not case-sensitive the find function shouldn't default to or even be case-sensitive neither [while a checkbox "case-sensitive" in find dialogue would be nice]
We can close this ticket after these two are done (and add another low-priority one for Regex ;-)
Simon
[r160] adds further tweaks to the search action:
Related
Commit: [r160]
Looks good but the bug with the wrong position [and mark/highlight] is still there. I've discovered the reason:
Simon