On Sun, Jun 06, 2004 at 11:40:15AM -0400, Andrew Pimlott wrote: > On Sun, Jun 06, 2004 at 10:39:26AM -0400, Thomas Dickey wrote: > > Looking at the code, I think the answer is that in initializing the > > active-icon logic it modifies the flags there - affecting the regular > > widget as well. (This is from code dating back to before I started > > working on xterm). The relevant chunk is > > > > /* since only one client is permitted to select for Button > > * events, we have to let the window manager get 'em... > > */ > > values->event_mask &= ~(ButtonPressMask | ButtonReleaseMask); > > values->border_pixel = term->misc.icon_border_pixel; > > Could you explain how xterm reacts to clicks if it has these events > masked? What am I missing? It's not clear to me either (it's an aspect of the code that never required redesign, so while I know where it is and how it works, some things won't be apparent). My guess is that since the mouse actions are bound to the vt100 widget (via the translations resource), that's why xev isn't seeing them - they're being caught at a different level of the widget hierarchy. xterm also modifies the mask when the application mouse protocol is in effect - but that doesn't seem to affect what xev can observe. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net
Attachment:
pgppEWKaDN_RV.pgp
Description: PGP signature