> > I wonder if we need to explicitly unregister the fltk window classes > from the Windows context and then re-assert them, or maybe register them > with a different name each time, or something...? > > > I am not sure if the entire endeavor will ever work. It's a long time ago > that I used the PS plugin API, and it was quite limiting. I believe that > there is a good reason for that: it is close to impossible to have > independent UI systems running within one application. > > Even though FLTK is of course based on the same core libraries as > Photoshop, there can be only on master. This master captures all the > events sent from the OS and decides if they are sent on or not. FLTK > requires a lot of events to function correctly, but if Photoshop snaps > those events away before they reach FLTK, FLTK will never function > correctly.
Agree. But the kicker here is that it (at least appears) to work perfectly the *first* time that the fltk window is shown. Then subsequent attempts to show the fltk context fail... So I do wonder if there's something we can do to make every time just like the first time, and hence at least give the appearance of working Just Right (even if under the covers it is all a bit suspect!) SELEX Galileo Ltd 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
