Re: [MiNT] Keyboard-problem with XaAES helmut-branch

["Helmut Karlowski" <helmut.karlowski@ish.de>]

Jo Even Skarstein wrote:

> On 06/27/2010 11:10 PM, Helmut Karlowski wrote:
>
> >> I guess I'm right. Now taskbar was in select-mode and everything went
> >> down the drain ..
> >>
> >> So leave away the console-output for a test.
> >
> > Now I can repair it by clever Ctrl-Q-pressing ;)
> >
> > Press Ctrl-Q when taskbar does console-output!
> >
> > I'm not sure if this can really be solved, it's the old RAW/COOKED-problem.
>
> It does not happen with an older version of XaAES. With a kernel from
> September and the current XaAES it does happen. I have yet not (IIR)
> tried an older XaAES with the current kernel.
>
> Anyway, there must be a solution. Ctrl+S is probably the third most used
> (after Ctrl+C/V) key-combination used in GEM apps.

Yes, but normally GEM-apps don't write to console extensively. This is
only possible under MiNT and toswin. I guess you can set your console to
raw-mode, but I cannot find it atm (I used tcsetpgrp or similar, but I'm
not sure if it really would work).

Maybe I increased the select-timeout in the XaAES-loop, so the RAW-mode
is set less frequently, I dont know. I'll look if there has anything
else changed.

There should be a fix to set all XaAES-clients' tty into raw
automatically. But this might have side-effects and has to be done right.


It may be worth a try to test this with a real old XaAES (maybe the one
from afros from 2008).


-Helmut