> I think the problem Ian is talking about is a different one; > how the event to handle() is being saved by the app in 'evt', > and how subsequent events are overwriting that value, messing > up the logic in the timer callback triggered code that checks > that 'evt' value. > > So Ian's highlighting a different issue here, not really > related to the Fl::event*() calls. > > I'm not sure, but I'm thinking the snapshotting of "evt" > in the app can maybe be removed, since the callback() should > only be invoked in this case due to an FL_PASTE. > > If it's not unique to FL_PASTE, then maybe a separate callback > should be setup, specific to DND.
Yes, I think I concur, the snapshot of "evt" is not really helping us much, and actively "breaks" things on win32. If I *only* update "evt" on FL_PASTE (thereby making it useless!) the win32 code then runs just fine, so I'd imagine it would work fine with it removed entirely. SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
