RE: Workaround for <Ctrl+F> and <Ctrl+N>

Hello Eric,

Thanks for the suggestion on combining the macros; I may do that. What I
would really like is for you guys to include this functionality in the base
commands so I would have no maintenance for these macros at all <big grin>.
BTW, do you know of an easy way that I could add this functionality to the
<Ctrl+U> LP_FINDPREV function?

You make an interesting point on the nameing of macros. I was under the
impression that to execute a macro that you actually had to specify MACRO
MACRONAME so that there could be no mistaking a macro for a command. Thanks
for clearing that up for me. It would also be just good practice to add a
standard prefix to the macro names to eliminate any possible confusion with
any new macros shipped in a future release.

Thanks again, Eric.

Brian

-----Original Message-----
From: code400-l-admin@midrange.com
[mailto:code400-l-admin@midrange.com]On Behalf Of esimpson@ca.ibm.com
Sent: Wednesday, November 28, 2001 9:22 AM
To: code400-l@midrange.com
Subject: Re: Workaround for <Ctrl+F> and <Ctrl+N>



Brian,

I noticed that the two find macros are very similar.  You could just have
one macro which takes a parameter to indicate to use LP_FINDCHANGE or
LP_FINDSEL (then you only have one file to maintain).  In your profile.lx,
you would specify the parameter on the Ctrl+F and Ctrl+N settings.

 'set action.c-f MACRO MYFIND'
 'set action.c-n MACRO MYFIND NEXT'

You might want to not call your macro 'FIND'.  By doing so, any other macro
that tries to use the editor 'FIND' command will be calling your macro and
might not get the expected results.

Eric Simpson
WebSphere Development Tools for iSeries
IBM Canada Lab - D1/140/8200/MKM
Phone:  (905) 413-3226,  Tie-Line:  969-3226,  Fax: (905) 413-4850
Email:  esimpson@ca.ibm.com