× 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.



For those inspired by Eric's articles, and accordingly inclined to extend LPEX, here's an action which will clear the "Find" field whenever the live-find dialog comes up:

  lpexView.defineAction("findAndReplace", new LpexAction() {
   public void doAction(LpexView view)
   {
    view.doCommand("set findText.findText \"\"");
    view.doDefaultAction(view.actionId("findAndReplace"));
   }
   public boolean available(LpexView view)
   {
    return view.defaultActionAvailable(view.actionId("findAndReplace"));
   }
  });

Vern Hamberg wrote:
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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.