MacArthur, Ian (SELEX) (UK) wrote: > >> >> Ya, I wasn't sure what the purpose of recording the event >> value was, or why the timer callback didn't just directly >> call dnd_open(), ie: > > IIRC, Alvin wanted to pop a confirmation dialog box, and doing that in > the callback was messing with the DnD badly - so the timeout was a way > to handle the DnD then pop the dialog safely outside the callbacks > context. > > > > 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. > ********************************************************************
Yup, that's correct. That said, if confirmation isn't required for the drop, then calling the callback directly in handle() works. That's what I used to do until the first time I called fl_choice() in my callback. :) In addition to that, I think calling dnd_open() directly prevents having multiple Fl_DND_Box widgets in the same app since the callback is static? For example, I have an app where I have two Fl_Scrolls. Each scroll has its own Fl_DND_Box. This way I can load a file in each using DND. -- Alvin _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
