On Fri, Jun 29, 2001 at 06:38:24PM -0400, Dan Espen wrote: > Dominik Vogt <fvwm-workers@fvwm.org> writes: > > On Fri, Jun 29, 2001 at 02:27:38PM -0400, Dan Espen wrote: > > > Dan Espen <[EMAIL PROTECTED]> writes: > > > > Dominik Vogt <fvwm-workers@fvwm.org> writes: > > > > > On Fri, Jun 29, 2001 at 10:36:02AM -0400, Dan Espen wrote: > > > > > > Ok, heres a trace: > > > > > > > > > > I'm not quite sure what I should see in this trace. To me, it > > > > > looks like a random piece of code recorded in a log file. Is this > > > > > meant to demonstrate one of the busy wait cycles? If it is, it > > > > > contains neither the start nor the end of the cycle. > > > > > > > > It is meant to demonstrate the cycle. > > > > > > > > I thought when it went from XQueryPointer at line 371 in menus.c > > > > back to the same location I had the whole cycle. > > > > > > In the sample I sent, it seems to fake a MotionNotify event > > > (line 1539, menus.c) and then start querying the pointer, I think > > > its looking for a release event. > > > > > > If it still looks bad to you, I'll redo it. > > > I might have inadvertantly moved the mouse while trying to get gdb > > > to operate. > > > > Probably. A cycly should start at the beginning of the loop in > > MenuInteraction(). > > Attached is a new trace. > > The while loop in menus.c starts with: > > flags.do_popdown_now = False; > > thats line 1427 in this trace. > > You will see that twice in the attached trace.
What you noticed is that fvwm periodically bumps out of the loop where it waits for events (Each time the PopupDelay is over) and checks if something has to be popped up. In the process, XQueryPointer is called three times. This happens every 150 milliseconds, so this should hardly be noticeable. I'll rewrite a bit of code so that it only needs to call XQueryPointer once. Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
