These are difficult to get right. I suspect that some of the fixes
recently submitted undid previous cursor positioning fixes.
I just inspected the code, and the logic for cursor positioning is
pretty sophisticated (read: appropriately complicated for speaking an
IBM protocol *grin*). There *is* code there to handle all of the odd
cases, so it's that something is broken rather than unimplemented.
Can I get a couple of tracelogs here, with descriptions of where the
cursor should end up? (email directly to [EMAIL PROTECTED] - don't
spam the list).
Remember, tracelogs contain your login password, so don't send it if you
aren't comfortable with that (or make a temporary user or something).
-Jay 'Eraserhead' Felice
([EMAIL PROTECTED])
P.S. As for the GUI issues mentioned, I hope the python bindings are a
step towards that. I hope to rewrite gnome-5250 in python so that we
can add high level features easily. I figure if binary size or memory
footprint is important, people won't be usingthe gnome/gtk+ versions
anyway.
P.S.S. To the person who was having trouble with F11 - it's fairly
typical for your window manager to trap F11 to bring up a window menu or
something (WindowMaker and AfterStep both do, at least). Check the
configuration of the window manager to make sure that it isn't stealing
the keystroke.
+---
| This is the LINUX5250 Mailing List!
| To submit a new message, send your mail to [EMAIL PROTECTED]
| To subscribe to this list send email to [EMAIL PROTECTED]
| To unsubscribe from this list send email to [EMAIL PROTECTED]
| Questions should be directed to the list owner/operator: [EMAIL PROTECTED]
+---
