[Xevie] Re: My current design efforts

[Keith Packard]

Around 9 o'clock on Oct 4, Deron Johnson wrote:

> I'm currently investigating an approach which has the X server sending
> events to the Display Server to do the pick and the Display Server sends
> the events back to the X server to do the grab processing and event
> propogation. If the event is destined for an X window, the event is sent to
> the event client. But if the event is destined for a 3D object, the event
> is sent back to the Display Server for further propogation.

Ok, that seems like a good direction to try.  If we do have too much 
latency in the 3D path, perhaps we can investigate sending a 'hint' along 
to the DisplayServer as to whether the event could be affected by a grab; 
that way simple motion won't have to make another pair of context switches 
most of the time while button events wind their way back and forth.

> So I'll probably only go that route if the non-shared-memory-picking
> approach has too great a latency.

Let's hope it works then -- it seems a lot more straightforward than our 
other alternatives.

> But I still wanted to know why you said that you wanted to support
> systems that don't support shared memory. What type of systems are
> you talking about?

It would be nice if Xevie could work with the event redirection client 
running on a separate address space.  Otherwise, we'd be adding the first 
ever non-network capable extension; a distinction I'd certainly like to 
avoid...

-keith


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
Url : http://freedesktop.org/pipermail/xevie/attachments/20041004/c3c3d981/attachment.pgp