Re: Bug Report: Locking X11 with FOX

Michal Suchanek wrote:

This is not FOX specific. GTK also uses menus that grab the X server
and if the application is busy and fails to remove the grab X server
is grabbed for a while before the application gets around to removing
the menu.
  

I beg to differ about the specifics of this case. I fully understand a grabbed server with no attention given to the event loop; all window systems are vulnerable. However, in my example, the "chore" quickly reduces the CPU load to 0 and the grab remains and mouse events are (seemingly) ignored. (I have evidence they are not ignored, just mishandled.) IMHO, it is a code path problem. My best guess is that it is caused by XLib's handling of the incoming events when they stack up; maybe XLib is combining events in some way that:

1. does not occur when the FOX polling loop is removing events at normal speed (because they don't stack up), and
   
2. confuses FOX into not properly setting up internal state such that when the server is grabbed the events are not properly dispatched.

I know exactly how to 100% reliably get FOX to exhibit #2. I've posted about it before. See my response to Jeroen for more.

-- 
Hal Brand
JCATS Chief Architect
Lawrence Livermore National Laboratory
7000 East Ave, Livermore, CA 94550-9234
Phone: 925-422-6312
Email: brand1@...

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Foxgui-users mailing list
Foxgui-users@...
https://lists.sourceforge.net/lists/listinfo/foxgui-users