VOGONS


First post, by emendelson

User metadata
Rank Oldbie
Rank
Oldbie

Thanks to the generous help of many members of this forum, I'm able to use a custom build of DOSBox as the basis for a system that runs WordPerfect for DOS with more screen options and flexibility than it ever had under real DOS.

This system has only one minor problem, and I wonder if there is any way to patch SVN that might help to fix it. I understand fully that this problem may not be relevant to any games, and so it is absolutely NOT something that I am asking the developers to spend time on.

Here is the problem. It occurs many times when WordPerfect switches video modes - whether from graphic to text mode, or the reverse, or when a program that runs in 25-line mode closes and my build switches back to its default 43-line mode. What happens is this: the last keystroke that I pressed before the switch in video mode gets repeated twenty or thirty times after the modes are switched.

So, for example, if I exit the WordPerfect printer definition program by typing "Y" to the prompt that asks if i want to quit, a long string of "y"s appears at the C:\ prompt after the program closes.

Or, if I switch from WordPerfect 6.x's text mode to graphics mode, by pressing Ctrl-F3 to bring up the "Screen" menu, and then G for graphics mode, a long string of "g"s get typed into the editing window after the program switches into graphics mode.

I don't know whether there is a solution to this, but I wonder if it might be possible to patch SVN so that the keyboard buffer is cleared whenever the video mode get switched.

Or is any other solution possible?

Thanks for any help or suggestions.

Reply 1 of 2, by Qbix

User metadata
Rank DOSBox Author
Rank
DOSBox Author

think this is a problem of SDL, at least it was last time we checked.

Water flows down the stream
How to ask questions the smart way!

Reply 2 of 2, by emendelson

User metadata
Rank Oldbie
Rank
Oldbie

Thanks for this. I'll learn to live with this, and hope the SDL developers eventually fix it.

For what it's worth, the problem occurs far more often on my OS X build than on my Windows build. Possibly the MacPorts version of SDL has more problems than the Windows/Linux versions.

Thanks again for clarifying this.