> It doesn't appear that the way fltk is designed that you > could ask a widget during a wait loop if it was clicked, > double clicked, etc.. So right now, I just have a call back > that sets a global structure that flags the widget and type > of click, then at the end of the wait loop, the structure is > cleared. That is fine for that, but now I have something > that I need to add taht is detached from the app, a class > that gets passed x,y,w,h area available for it and the > buttons the main window has, it has to be able to determine > when they are clicked, if the widget held the click state, it > be easy, but the only way I see now is for me to have to pass > the click structure too. How is fltk designed to work for > deteting clicks when you only know the widget?
I'm sure I have not understood your question (I'm sure I have not understood your question...!) - can you clarify a bit more what you are actually trying to do (as well as, and distinct from, how you are currently doing it!) please. It sounds as if you are maybe not using the fltk events in the intended fashion, so are coming at this from a direction that does not sit comfortably on the fltk model. If you can explain what you are trying to achieve, we can maybe think about how to do that in the fltk model. 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
