<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to 2: Be selective about X events.</title><link>https://sourceforge.net/p/openglean/feature-requests/2/</link><description>Recent changes to 2: Be selective about X events.</description><atom:link href="https://sourceforge.net/p/openglean/feature-requests/2/feed.rss" rel="self"/><language>en</language><lastBuildDate>Sat, 05 Feb 2005 04:43:21 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/openglean/feature-requests/2/feed.rss" rel="self" type="application/rss+xml"/><item><title>Be selective about X events.</title><link>https://sourceforge.net/p/openglean/feature-requests/2/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The code presently just turns on all X event types,&lt;br /&gt;
carte blanch---whether or not a given event is of&lt;br /&gt;
interest.  All windows have ~all events turned on, all&lt;br /&gt;
of the time.&lt;/p&gt;
&lt;p&gt;This makes it harder to debug, since you get spammed,&lt;br /&gt;
for example, by passive mouse motion, even if you don't&lt;br /&gt;
care where the mouse is.&lt;/p&gt;
&lt;p&gt;Instead of turning on all events all of the time,&lt;br /&gt;
an event-set normalization routine could be called&lt;br /&gt;
everytime you set/unset callbacks.  In callbacks.c,&lt;br /&gt;
this could be stuffed into the window-callback-setting&lt;br /&gt;
macro.  That would take care of *most* of the cases;&lt;br /&gt;
I can only think of one other place, offhand, that&lt;br /&gt;
would need to set the event mask (when windows are&lt;br /&gt;
being destroyed, we clear the callbacks and should at&lt;br /&gt;
that point clear the mask, too).&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Richard Rauch</dc:creator><pubDate>Sat, 05 Feb 2005 04:43:21 -0000</pubDate><guid>https://sourceforge.net07eef9a2bc4c128b092f64d33a7f88ed4e75a71c</guid></item></channel></rss>