🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.sys.next.programmer
1 messages
1 total messages Started by J. G. Gregory Sat, 26 Sep 1992 16:09
Using mousemoved events vs. GDB
#1616
Author: J. G. Gregory
Date: Sat, 26 Sep 1992 16:09
33 lines
1694 bytes
I'm having a problem turning off mousemoved events while my application is  
stopped in GDB.  Any help or suggestions would be greatly appreciated.

My application has a mode that turns on mousemoved events (and it's on most of  
the time).  Unfortunately, the application is not yet bug-free, and so  
occasionally crashes into the debugger while in this mode.

Now after moving the mouse for a little while,  I start getting zillions of  
messages like the following in the Console window.  Since the system is  
spending so much time generating the messages, it's hard to do much debugging.

Sep 14 11:22:37 proforma WindowServer[150]: Event discarded: window 39: 5 @  
(1.090716e+15,1.660258e-308), 0.

I can understand that the events aren't being processed, and so the event queue  
fills up.  What's puzzling is that calling the following method from within GDB  
doesn't turn them off:

- gdb
{
   [window removeFromEventMask:NX_MOUSEMOVEDMASK];
   // Desperation move
   DPSDiscardEvents(DPSGetCurrentContext(), NX_ALLEVENTS);
   return self;
}

Executing this method does change the window's event mask, but it doesn't seem  
to stop the events from being generated.  This same code (without discarding  
the events) executed while the app is actually running will stop the mousemoved  
events.

Thanks in advance,
--J Gregory
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads