KpyM Telnet/SSH Server - Forum
| Text jumping bug. |
| linred |
Text jumping bug. |
Jan 24 2010 13:36 |
| |
Dear Kroum, your KpyM is awesome! IЎЇd like to use it for my excel-like app that works with tables, but while exploring/scrolling tables cursor unexpectedly jumps to unexpected locations and sometimes strange ўА metasymbol appears.
There is a small program (C#, .NET Framework 2.0) that demonstrates this bug:
l0c41://blogsense.info/files/blogsense/ClubsBug.zip
This demonstration reads and writes cursor position many times. It works fine via KpyM if buff_height=0, but goes astray if buff_height=200 or so.
Please set refresh_delay=3 to increase the probability of appearing of the bug.
Several times I noticed this bug even while initial Ў°waitingЎ¦ 5Ў± counter counts down when I connect to server.
|
| Kroum Grigorov |
|
Jan 27 2010 06:38 |
| |
>This demonstration reads and writes cursor position many times
When scroll back is enabled ( buff_height not 0) KTS relies internally on the cursor position and a special character to calculate the changes on the screen.
So any app that manipulates the cursor pos will result in this problem. Depending on the intensity the cursor is moved this will hapen more or less often.
Kroum
|
| linred |
|
Feb 02 2010 16:25 |
| |
Do you have an advice on how application that manipulates cursor should behave to avoid spoiling of the screen? In other words, what kinds of manipulations are allowed? Maybe I should write buffer data directly via WriteConsoleOutput from kernel32.dll ?
Or maybe there are some clients (I use Putty) that collects its own scroll back buffer when the most top lines go out of screen (not only "Push erased text into scrollback"), so I could set buff_height=0
Thank you in advance!
|
| Kroum Grigorov |
|
Feb 03 2010 19:43 |
| |
> should behave to avoid spoiling of the screen
If you run KTS with scroll back buffer sooner or later you would spoil the screen. The best you can do is to run this without scroll back buffer or live with the possibility of spoiling the screen from time to time.
>that collects its own scroll back buffer when the most top lines go out of screen
I don't think such clients will work, the point of no scroll back is to limit the changes to the current screen only the client will never know there were lines that go out of screen.
Kroum
|
© 2007 - 2008 Kroum Grigorov
