On Fri, Feb 24, 2023 at 11:34 AM Kenneth Pettit wrote:
> Hey Steve,
>
> I think the operative words in your email contributing to slowness are
> "windows machine" (tee hee hee). But seriously ... Windows? Do people
> still use Windows in 2023? (Sorry, just can't help myself).
>
> Ken
>
>
Hey n
On Fri, Feb 24, 2023 at 11:34 AM John R. Hogerhuis wrote:
>
> Yes. Sounds like something is broken or badly written. Some non-blocking
> loop.
>
> Generally a program waiting on terminal input has absolutely nothing to do
> but wait for the OS to wake it up with a character.
>
> -- John.
>
And
MS-DOS Forever!!!
On Fri, Feb 24, 2023 at 2:34 PM Kenneth Pettit wrote:
> Hey Steve,
>
> I think the operative words in your email contributing to slowness are
> "windows machine" (tee hee hee). But seriously ... Windows? Do people
> still use Windows in 2023? (Sorry, just can't help myself).
On Fri, Feb 24, 2023 at 11:16 AM Stephen Adolph
wrote:
> Question for the crowd.
>
> I've got the mvt100 terminal in C# running well. It is compiled in Visual
> Studio.
>
> When I run in full screen mode, the cpu utikixlxation jumps to 50% and the
> response of the terminal is visibly slow.
>
>
Hey Steve,
I think the operative words in your email contributing to slowness are
"windows machine" (tee hee hee). But seriously ... Windows? Do people
still use Windows in 2023? (Sorry, just can't help myself).
Ken
On 2/24/23 11:15 AM, Stephen Adolph wrote:
Question for the crowd.
I've
Question for the crowd.
I've got the mvt100 terminal in C# running well. It is compiled in Visual
Studio.
When I run in full screen mode, the cpu utikixlxation jumps to 50% and the
response of the terminal is visibly slow.
I get that the screen updates take time, but really? My windows machine
