> Now, if push on the button widget, the button will in a > pushed status, but I do not want this pushed status.
Can you clarify this, please? Are you saying that: A) The button stays down when you click it, even after you release the mouse? Or B) You *do not* want the button to visibly respond to being clicked on at all? > That's > means I do not want the button has any change if I pushed on > it. Is there any method to implement it? Well, that depends what the problem is. If it is (A) above, the button might be set as a "toggle" button (which will go down when clicked, and will not come back up until clicked again) in which case changing it to a "normal" button might help. A "normal" button will usually go down whilst the mouse is held down, but will come back up when you release the mouse. Unless... If the callback to a "normal" button takes a very long time to execute, and does not yield to the GUI queue, the button will go down and will stay down until the callback completes. If this is what is happening, you need to re-write your code. GUI code is even driven, and executing long processes inside a button callback is very bad practice. Instead, you need to have the button callback do some very minimal processing that will return from the callback promptly, and use that processing to trigger the long process, either in another thread, or via a timer or otherwise - but certainly the long process should not be executing in the button callback. If (B) is what you want - i.e. you do not want any visible indication that a button has been clicked on - then I would caution against that as a design idiom. It is *very* helpful to the end user to get some visual feedback that their action has been detected, particularly if the resulting process will take some time to run. However, if you want to do that, it is pretty easy - you just derive your own button type and re-work the draw and handle methods accordingly. Greg has a worked example of making and drawing your own button classes here: http://www.seriss.com/people/erco/fltk/Fl_Matte_Button/ > my fltk is v2.0 Yes - though you already know that I suggest you switch to fltk-1.1 until you are more familiar with the tool. You will likely get more comprehensive support using 1.1 than 2.x... 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
