On 2/17/2015 5:01 PM, John Yeung wrote:
My contention has always been that positioning the cursor just beyond
the last nonblank character is not an SEU function.
Well yes, I completely agree! I'm afraid I've been talking past you in
my zeal to stick my foot into my mouth.
Ever since I had a dedicated End key on my keyboard, I have mapped my
5250 session to make it do the same thing the End key does in Windows
and Linux: move to the end of the line. That's well over 20 years. I
like that the End key does the same thing on all the platforms I use.
This includes SEU: for 20+ years, if I press the End key in SEU, the
cursor invariably moves to the end of the line.
Also for 20+ years, when I open a source member in Code / WDSC / RDi,
when I press the End key, the cursor invariably moves to the end of the
line.
At some point, RDi has developed at least one scenario where the End key
behaves unexpectedly. I can consistently cause that behaviour by
touching a member with SEU, then opening it in RDi. That is the only
reason I bring SEU into this; to demonstrate a 100% reproducible scenario.
You are 100% correct; the End key behaviour isn't an SEU function; it's
a key mapping in my emulator which works for all 5250 input capable
fields. I like it that way because it's consistent across platforms.
The issue at hand is that it is now inconsistent with RDi.
midrange.com
