[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Get global X events and save your environment!
From:       Stefan Kombrink <katakombi () gmail ! com>
Date:       2007-07-08 20:05:13
Message-ID: 200707082205.13606.katakombi () web ! de
[Download RAW message or body]

On Saturday 07 July 2007 15:45:42 Lubos Lunak wrote:


>  Actually, the real main issue is that usually no client can connect, since
> it's disabled by default.

I think distributions won't change that since it might be considered as 
security weakening.

>  I don't think the code should use threads, because, in the first place, it
> actually doesn't need them, as there's nothing blocking; another reason is
> that one should call XInitThreads() for that to work, which generally does
> not really work and causes all kinds of problems.

Isn't the XNextEvent blocking? Anyways one would need an ClientMessage to quit 
the thread.
Can you think of a way to do the XEvie stuff without a QThread?

>  Yes, it would be nice to have a shared implementation for this. Especially
> the copy&paste is pretty bad :(. I just don't think it should use Xevie -
> it should use the code that kdesktop has, plus (very) recent X.org has an
> XSync counter that can be used to detect user inactivity. Which should be
> sufficient for all the cases listed above, except for KSynaptics, if I'm
> getting it right :-/.

What kind of mechanism does kdesktop use?
Is it possible to catch key events in idle mode using XSync?
I got no idea how the XSync stuff works. I once read the documentation and 
felt like it would be necessary to modify XOrg? (like predefined event 
counter or something like that)
If that is possible I'd immediately agree to use that.

Also agreed: In my use cases you get away with (in)activity detection, but the 
follow-up from KDE usability shows that there are other use cases as well

Regards,
 Stefan K.

-- 
Warning! Insufficient or missing coffee in module "STOMACH". 
User halted.
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]