Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
Moderator: | STAR::VATNE |
Created: | Mon Oct 30 1989 |
Last Modified: | Mon Dec 31 1990 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 3726 |
Total number of notes: | 19516 |
Note 515 of decwindows_ft1 and 980 of _old talked about the problem of fill_highlight going away when the cursor moves out of a pushbutton. It was QAR'd but may have been dropped because there was a workaround. My question is whether or not it is a bug that highlight goes away when the cursor leaves a pushbutton? If not a bug then could someone explain why it acts that way. If it is a bug is it fixed or still on the list or forgotten. To demonstrate add a setvalues (DwtNfillHighlight,1) to the helloworld activate routine.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
1090.1 | By design | RTL::MCOLLINS | Fri Jul 14 1989 13:24 | 27 | |
The highlight of a pushbutton is used to indicate the 'armed' state. The Style Guide default semantics are that a button down in a pushbutton arms it, a button up activates iff armed. A leave window event disarms a pushbutton. eg: the default translations look something like this (edited for clarity) "~Shift ~Ctrl ~Meta ~Alt<Btn1Down>:\ HIGHLIGHT()\ highlight & arm DWTPBARM()\ None<Btn1Up>: DWTPBFILLUNHIGHLIGHT()\ unhighlight DWTPBACTIVATE()\ activate iff armed DWTPBDISARM()\n\ force disarm Any<LeaveWindow>: DWTPBFILLUNHIGHLIGHT()\ clear highlight DWTPBDISARM()"; force disarm We could argue about the 'correctness' of these semantics but that is what it is set up to do. Why it's this way is mostly because that's what the Style Guide people wanted at the time. Mike Collins |