Hi; On Sun, 2008-07-13 at 12:30 +0200, Andy Wingo wrote: > > I think we should probably handle MapNotify / ConfigureNotify events too > at some point, given that TFP is (always?) used to swallow an > application's window. I had the start of a patch here: > > http://bugzilla.o-hand.com/show_bug.cgi?id=1020
Yes I agree, I just held off an applying (or even reviewing it) for 0.8.0. (Wanting to get current code under control and not further block on 0.8 with more features). We should be able to get it into 0.8.2 I think though - it shouldn't change any API. > > Ah, coding while drunk, that. Probably would be good to have "mapped" > and "destroyed" properties on the actor as well, so you could just > connect to notify::foo signals to do somethingorother, but you still > have the pixmap so you can do e.g. animations for the window being > destroyed. I'll take a look. > > While we're on the topic, I saw another problem in my app: > > X Error of failed request: BadWindow (invalid Window parameter) > Major opcode of failed request: 150 (Composite) > Minor opcode of failed request: 3 () > Resource id in failed request: 0x600003 > Serial number of failed request: 262 > Current serial number in output stream: 262 > > Adding an XSync() in the trapped-errors UnredirectWindow block fixed > this. Does this make sense? > Yes - have committed this. Thanks! == Matthew -- To unsubscribe send a mail to [EMAIL PROTECTED]
