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

[Jo Even Skarstein <joska@online.no>]

On 06/27/2010 09:07 PM, Helmut Karlowski wrote:

>> Sorry, it's 's' not 'S'. Tried SIGCONT but it did not make a difference.
> 
> Then it's select, which is ok. Next version will have longer entries for
> STATE.

Does this mean that Taskbar itself is waiting in Fselect() (which it
does at some points, but only to create some necessary delays using
Fselect(millis, NULL, NULL, NULL)) or that XaAES is waiting on Taskbar's
behalf?

>> relate to in MiNT before. According to the Task Manager, all processes
>> have pgrp == pid, except the kernel threads which all have pgrp == 0.
> 
> On my TT currently toswin has pid 13 and pgrp 1 (the one of XaAES). On
> aranym taskbar also has the pgrp of XaAES as all XaAES-clients have.

The kernel and XaAES I'm using is yours from 11/6. Has things changed
since then? Maybe a more recent version would help.

>> Taskbar does indeed wait for keyboard events. Disabling that does not
> 
> Using Bconin?

No, plain AES events all the way.

>> I most definitely have ;-) I will send you the current version later
>> tonight.
> 
> Ok - I wait for the third announcement ;)

Hehe! It's not so easy when the Milan is not permanently online. But
take a look in your mailbox now.

> But I would first like to know why your pgrps are different.

Me too.

Jo Even