Hi to all,
I'm still not clear with the behavior of some dialog elements and what FWH users want.
Understanding that there is a standard Clipper and a standard windows behavior and they are different in some points:
Clipper shall function as follows:
- ENTER key: focus changes to next dialog element
- Entering an element with TAB or ENTER key: the text isn't selected automatically
- Hot key of a BUTTON: the action of the button has to be executed, not only setting the focus
Windows shall function as follows:
- ENTER key: executes the action of the standard button
- Entering an element with TAB or ENTER key: the text is selected automatically
- Hot key of a BUTTON: the action of the button has to be executed, not only setting the focus
Of course, it's quite possible that there are some other differences, I don't notice until now.
Also understanding, that now the Clipper behavior is active, but it don't funcion as expected in some points:
- Entering a combo box: all text is selected automatically
- Hot key of a BUTTON: sets only focus
In older versions of FWH, the behavior was more windows like, but also not in all points, e. g. see viewtopic.php?f=3&t=19181&p=107044.
Sample code for testing:
Conclusions:
- Please adjust the Clipper behavior.
- Maybe it's possible to implement a switch to change from Clipper to Windows behavior, so the end user can choose
- Make both behaviors as standard as possible.
I'm still not clear with the behavior of some dialog elements and what FWH users want.
Understanding that there is a standard Clipper and a standard windows behavior and they are different in some points:
Clipper shall function as follows:
- ENTER key: focus changes to next dialog element
- Entering an element with TAB or ENTER key: the text isn't selected automatically
- Hot key of a BUTTON: the action of the button has to be executed, not only setting the focus
Windows shall function as follows:
- ENTER key: executes the action of the standard button
- Entering an element with TAB or ENTER key: the text is selected automatically
- Hot key of a BUTTON: the action of the button has to be executed, not only setting the focus
Of course, it's quite possible that there are some other differences, I don't notice until now.
Also understanding, that now the Clipper behavior is active, but it don't funcion as expected in some points:
- Entering a combo box: all text is selected automatically
- Hot key of a BUTTON: sets only focus
In older versions of FWH, the behavior was more windows like, but also not in all points, e. g. see viewtopic.php?f=3&t=19181&p=107044.
Sample code for testing:
#include "FiveWin.ch"
function Main()
local oDlg, nValue := 1, cTest := "Test", cTest2 := "Test2", cCombo := "combo"
DEFINE DIALOG oDlg
@ 1, 1 RADIO nValue ;
ITEMS "&One", "&Two", "T&hree"
@ 1, 10 COMBOBOX cCombo ITEMS { "1", "2", "3" } SIZE 40, 120 STYLE CBS_DROPDOWN
@ 2, 10 GET cTest SIZE 70, 10
@ 3, 10 GET cTest2 SIZE 70, 10
@ 3, 10 BUTTON "O&k" ACTION oDlg:End()
ACTIVATE DIALOG oDlg CENTERED
return NILConclusions:
- Please adjust the Clipper behavior.
- Maybe it's possible to implement a switch to change from Clipper to Windows behavior, so the end user can choose
- Make both behaviors as standard as possible.
Windows 11 Pro 22H2 22621.1848
Microsoft (R) Windows (R) Resource Compiler Version 10.0.10011.16384
Harbour 3.2.0dev (r2008190002)
FWH 23.10 x86
Microsoft (R) Windows (R) Resource Compiler Version 10.0.10011.16384
Harbour 3.2.0dev (r2008190002)
FWH 23.10 x86
