Debugging drags, mouse capture / pointer grab, kdevelop3 freezes

[Alex Bligh]

Pierre-Paul,

Pierre-Paul Lavoie wrote:
>> This makes it really hard to debug drags. Now I'm not sure why X is
>> carrying state between two apps (I'm not an X guru), or indeed whose
>> responsibility it should be to clear things up. Any ideas for a
>> fix or work-around?
>>
>> Alex
> 
> This is because of the Xlib call XGrabPointer [1]. The event processing 
> depends on the pointer_mode and owner_events. There' not much KDevelop 
> could do afaik. The application is being paused while it have an 
> exclusive access to the mouse pointer.
> 
> Usuallly, when you develop applications such as a window manager, you 
> will use a nested server. You should try running your application in 
> Xnest and debug the application from your normal desktop/server.

Thanks. That works, and gave me the rather simpler idea that I
could run two X Servers at once, and switch between them by
virtual console.

However, can kdevelop really not make a useful attempt to sanitize
its X environment? Is there not some call to X which will end
/any/ grab pointer, as you know if the pointer /is/ grabbed then
nothing's going to work, the app will inevitably hang.

Alex

-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«