Isn't that like a field exit thing?

Let me know if it is cause I think I had them make some changes for me to do
what field exit does on a terminal.

> -----Original Message-----
> From: Buck Calabro [mailto:Buck.Calabro@commsoft.net]
> Sent: Wednesday, June 05, 2002 1:17 PM
> To: linux5250@midrange.com
> Subject: RE: [LINUX5250] Keyboard mapping - feedback
>
>
> OK, I added the following to the key down table in winterm.c
> { VK_SHIFT    VK_LEFT,         K_PREVWORD  , 0, 1 },
> { VK_SHIFT    VK_RIGHT,        K_NEXTWORD  , 0, 1 },
>
> and it maps to the appropriate functions just fine.  Alas,
> the function
> doesn't do what I want it to do.  They move the cursor to the
> next/last
> non-blank character.  I would like to move to the next/last
> field whether
> it's blank or not (like the option column in PDM.)
>
> So, I have a look around to see where the K_PREVWORD is used, and by
> burrowing in enough places, I see that PREVWORD is called in
> display.c and
> implemented in dbuffer.c.  When I get a chance, I will try to change
> tn5250_dbuffer_prevword to go to the field boundary, not just
> to the next
> non-blank.
>
> Thanks for the tips.  I will let the list know how I make
> out. (Green screen
> guy trepidation showing.)
>   --buck
> _______________________________________________
> This is the Linux 5250 Development Project (LINUX5250) mailing list
> To post a message email: LINUX5250@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/linux5250
> or email: LINUX5250-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/linux5250.
>


This thread ...


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

This mailing list archive is Copyright 1997-2019 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].