× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



In the seu profile, Ctrl-F and Shift-F2 (same as F14 in 5250 session) are supposed to be linked to the find key action, which, by the documentation, is supposed to "move the cursor from the text area to the find line". This is the behavior of F14 in PDM, where it lets you set up the find string, e.g. Shift-F4 (F16 equivalent) is linked to FindNext, which is defined as "if the text stored in the findText.findText parameter is not a null string, the findNext action will move the cursor to the next visible instance of the text stored...". This is the same behavior as SEU, where the last search string will be located, if it exists farther down than your cursor.

It seems that the "find" action actually performs the "findNext" action, which does not seem right. There does not seem to be another choice to limit the behavior, as it is supposedly set to that minimum effect now.

Vern

At 11:35 AM 1/16/2004 -0330, you wrote:
Hi,

In WDSCi 5.1.0.1 when I edit an RPGLE member in LPEX editor 1.4.3 when
press CTRL+F to find, it searches for the last string I searched for
without offering me the opportunity to change it.  If the previous string
was found, I am repositioned to a different location in my source member
which can be very annoying.  CTRL+F should really only pop up the find
box, but not do the same action as the Find Next (shift+F4).

>From here I am forced to  use the editor command / to search which is
cumbersome, especially for subsequent searches (I have to press up arrow,
then enter).

This may seem trivial but being a developer myself, it is somewhat
confusing as to why there needs to be two methods of finding text in the
member, and I know that our other developers will have issues with this
because they lose their place in the code even before they have a chance
to search.

Is there a way to tell the CTRL+F command not to search right away.  If I
want to repeat a find, I will simply press Shift+F4.

Thanks,
Dean



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.