DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2360 Version: 2.0-feature [Not sure I'm doing this right... but here goes...] re: Events diagnostics. 'Tis done. And here's what we can now see. I'll tell you what I know about it in a sec, but notice that we get a 'MOVE' event from fltk with a null window pointer below. I'll group the events so that the XEvent that triggers the fltk response is at the top. fltk::Window = 0x0804B598, fltk::xevent = 21 ReparentNotify fltl::Window = 0x0804B598, fltk::event = 0 fltk::NO_EVENT fltl::Window = 0x00000000, fltk::event = 11 fltk::MOVE fltk::Window = 0x0804B598, fltk::xevent = 22 ConfigureNotify fltl::Window = 0x0804B598, fltk::event = 0 fltk::NO_EVENT fltk::Window = 0x0804B598, fltk::xevent = 19 MapNotify fltl::Window = 0x0804B598, fltk::event = 0 fltk::NO_EVENT fltk::Window = 0x0804B598, fltk::xevent = 9 FocusIn fltk::Window = 0x0804B598, fltk::xevent = 11 KeymapNotify fltl::Window = 0x0804B598, fltk::event = 0 fltk::NO_EVENT fltk::Window = 0x0804B598, fltk::xevent = 12 Expose fltl::Window = 0x00000000, fltk::event = 11 fltk::MOVE fltk::Window = 0x0804B598, fltk::xevent = 19 MapNotify fltl::Window = 0x0804B598, fltk::event = 0 fltk::NO_EVENT fltk::Window = 0x0804B598, fltk::xevent = 12 Expose fltl::Window = 0x00000000, fltk::event = 11 fltk::MOVE fltk::Window = 0x0804B598, fltk::xevent = 33 ClientMessage fltl::Window = 0x00000000, fltk::event = 11 fltk::MOVE ---------------- In version 1 I saw these FL_NO_EVENTS flowing through quite often and they are not a problem. You can set your callbacks to receive them when you select them (in fluid) to go off on [no event] and [always], or something to that effect. I can't remember exactly, but bottom line here is that this is normal behavior. But what I never did see is a null window pointer, especially one with a MOVE type. This may actually be ok in version 2. I don't know yet, but what I want to point out at this point is that WE CAN SEE!! :-) Here's the modified files to play with so far, if you so desire. Keep backups. Best to merge the code rather than replace your entire file, but live dangerously if you like. This should be ok with the "current" fltk v-2.0. (merged with r7513) If these files don't work for you, hang on. We'll get something to play with working eventually. [I'll try to send the files in another post.] ------------ Now comes the long journey... what do images, scrollbars and other widgets that aren't updating properly have in common? Why aren't they "getting the message" to update themselves. Well, scrollbars DO correct themselves when you resize the window. So that's where I'll start. Object = scrollbar, event = resize, and let's see how and why that works. This may take a while... Link: http://www.fltk.org/str.php?L2360 Version: 2.0-feature _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
