Hey list, On Sat 12 Jul 2008 01:39, Matthew Allum <[EMAIL PROTECTED]> writes:
> Hi; > > On Fri, 2008-07-11 at 19:32 -0400, Jason Tackaberry wrote: >> On Thu, 2008-07-10 at 01:15 +0100, Matthew Allum wrote: >> > Doh, TFP is waaaaay too painful. >> >> Yes but it's terribly useful. Please don't give up on it. :) >> > > :-) I agree. > > Hopefully its pretty much working everywhere now nearly as best it can. > I think the code/API could probably do with a little re-factoring at > some point but that can wait for now. 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 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. 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? Peace, Andy -- http://wingolog.org/ -- To unsubscribe send a mail to [EMAIL PROTECTED]
