RE: Shift+F4 "Find next" broken in LPEX editor

Ahh yes!  SEU's F14 for "Find".  Then F14 is probably okay to me in CODE
and LPEX.  I still think LPEX should be mapped like CODE for everything
else mentioned in the original post at the bottom though.

Thanks again,
Craig

** Rick wrote:
Oops.  That should have been 'F14 for search and F16 to repeat the
> last search.'

> -----Original Message-----
> From: Chevalier, Rick
> Sent: Friday, October 03, 2003 7:38 AM
> To: Websphere Development Studio Client for iSeries
> Subject: RE: [WDSCI-L] RE: Shift+F4 "Find next" broken in LPEX editor
>
>
> You're welcome.
>
> It took me a little while but the way I remember it is that they are
> mapped to the same keys in SEU.  F14 for search and F14 to repeat the
> last search.
>
> Rick
>
> > -----Original Message-----
> > From: craigs@xxxxxxxxx [mailto:craigs@xxxxxxxxx]
> > Sent: Friday, October 03, 2003 7:27 AM
> > To: wdsci-l@xxxxxxxxxxxx
> > Subject: [WDSCI-L] RE: Shift+F4 "Find next" broken in LPEX editor
> >
> >
> >
> >
> >
> >
> > Thanks Rick!  The shift+F2 worked.  I am a little confused
> > about all these
> > key mappings.  They just don't make any sense to me.  On the
> > "Source" drop
> > down menu, it says shift+F4 is "Prompt" and also "Find Next"
> > is shift+F4
> > except in the "Find" dialog.  F4 is "Prompt" as well.  It
> > seems they could
> > have made F4 be "Prompt" only and shift+F4 "Find Next" only.
> > Furthermore,
> > ctrl+F could be "Find" only instead of shift+F2 as well.  I
> think that
> > would free up more mappings for more options and make it a
> > little easier on
> > us.  Just make it like the mappings in CODE although I am not
> > sure why CODE
> > mapped shift+F2 and ctrl+F to the same function.
> >
> > Craig