Hi all,
In Eclipse(OEStudio)/windows/preferences/General/Keys we have these two animals:
But these don't work in an ABL editor :( And I hate that Find/Replace windows with its "Forward/Backward" Direction radio-set.
Any explanation why it does not work or how to fix it?
Note: Fortunately, the incremental search action (à-la-Firefox) does work (bound to Ctrl-J and Ctrl-Shitt-J)
/Sebastien L.
Hi Jean, I do not know what was the cause of this problem and do not even know how to reproduce it. I just tried again this morning without success, but I may not have more time to investigate it further.
How it happened: in the ABLEditor, I was wondering how to do find next/prev like we could in the old procedure editor (F9/shift-F9), found the standard key shortcut in the doc, then tried it but found out it did not work. At that point I asked the question on the forum. Later in the day it worked again. Perhaps it was due to the way perspectives and views were opened... dunno
Cheers
Note: many people ignore this shortcut and spend their life in this horrible find dialog ;)
Flag this post as spam/abuse.
found out that switching back an forth from OpenEdge Editor perspective to the Java Perspective has enabled these two shortcuts....
[mention:1742ab6f05dc44c8941c8fe6a42637b6:e9ed411860ed4f2ba0265705b8793d05] , based on your initial description and how it worked after you switching back and forth, it looks like we may have a little issue. Maybe good to report it to Support...
Hi slacroixak,
These two shortcuts work when ABLEditor is focused. For ex, in Find dialog provide text to find then click on ABLEditor. Now, try shortcuts Ctrl+K and Ctrl+Shift+K. It works.
-DivyaTheja
Hi Jean, I do not know what was the cause of this problem and do not even know how to reproduce it. I just tried again this morning without success, but I may not have more time to investigate it further.
How it happened: in the ABLEditor, I was wondering how to do find next/prev like we could in the old procedure editor (F9/shift-F9), found the standard key shortcut in the doc, then tried it but found out it did not work. At that point I asked the question on the forum. Later in the day it worked again. Perhaps it was due to the way perspectives and views were opened... dunno
Cheers
Note: many people ignore this shortcut and spend their life in this horrible find dialog ;)
Hi Jean, I do not know what was the cause of this problem and do not even know how to reproduce it. I just tried again this morning without success, but I may not have more time to investigate it further.
How it happened: in the ABLEditor, I was wondering how to do find next/prev like we could in the old procedure editor (F9/shift-F9), found the standard key shortcut in the doc, then tried it but found out it did not work. At that point I asked the question on the forum. Later in the day it worked again. Perhaps it was due to the way perspectives and views were opened... dunno
Cheers
Note: many people ignore this shortcut and spend their life in this horrible find dialog ;)
Flag this post as spam/abuse.
Hi Peter, now I know what happens:
I am the kind of guy that splits the Eclipse editor view in two (drag a tab folder to the right) to read two pieces of code at once. (of course, two is not always enough so I spawn another window with two others, but it's bot the point here)
If you press CTRL-F to find in the first editor (on the left side), then later do the same in the other editor (on the right), you get a 2nd Find/Replace small window.
However, later if you press CTRL-K in the first editor, then it tries to performs a find next action based on the content of the 2nd Find/Replace window as opposed as the content of the 1st, hence the confusion. The solution is to make the 2nd window appear again (do a dummy find in the 2nd editor if it was gone), then search what you want in the first editor (too bad if it find it), then click back in the first editor and press Ctrl-K. In other word, Ctrl-K uses the last Find/Replace window.
Note: this issue does not seem to happen in a standard Java Project when editing java code with a split view (I just tried with the Eclipse Kepler 4.3 of OES). Indeed, with Java, the first Find/Replace window is reused. So this is apparently a little OES problem. Should I report that?
Hi Peter, now I know what happens:
I am the kind of guy that splits the Eclipse editor view in two (drag a tab folder to the right) to read two pieces of code at once. (of course, two is not always enough so I spawn another window with two others, but it's bot the point here)
If you press CTRL-F to find in the first editor (on the left side), then later do the same in the other editor (on the right), you get a 2nd Find/Replace small window.
However, later if you press CTRL-K in the first editor, then it tries to performs a find next action based on the content of the 2nd Find/Replace window as opposed as the content of the 1st, hence the confusion. The solution is to make the 2nd window appear again (do a dummy find in the 2nd editor if it was gone), then search what you want in the first editor (too bad if it find it), then click back in the first editor and press Ctrl-K. In other word, Ctrl-K uses the last Find/Replace window.
Note: this issue does not seem to happen in a standard Java Project when editing java code with a split view (I just tried with the Eclipse Kepler 4.3 of OES). Indeed, with Java, the first Find/Replace window is reused. So this is apparently a little OES problem. Should I report that?
Flag this post as spam/abuse.