Guys:
On a dialog with a couple of says & gets, how can I:
1. Highlight in other color the current get ?
2. Move between fields with the ENTER key instead of the TAB key ?
Thank you.
FiveTech Support Forums
FiveWin / Harbour / xBase community
Board index FiveWin for Harbour/xHarbour How do I ... ?
Hello Hunter,
REDEFINE GET oGet1 VAR SOURCETEXT1 ID 100 OF oDlg UPDATE
oGet1:bGotFocus := {|| oGet1:SetColor( 16777215, 128 ) }
oGet1:bLostFocus := {|| oGet1:SetColor( 0, ) }
REDEFINE GET oGet2 VAR SOURCETEXT2 ID 101 OF oDlg UPDATE
oGet2:bGotFocus := {|| oGet2:SetColor( 16777215, 128 ) }
oGet2:bLostFocus := {|| oGet2:SetColor( 0, ) }
The Get-Fields inside the Resource, must be sorted to running Numbers.
A Return on a Focused Get, will move to the next one.
Best Regards
Uwe
REDEFINE GET oGet1 VAR SOURCETEXT1 ID 100 OF oDlg UPDATE
oGet1:bGotFocus := {|| oGet1:SetColor( 16777215, 128 ) }
oGet1:bLostFocus := {|| oGet1:SetColor( 0, ) }
REDEFINE GET oGet2 VAR SOURCETEXT2 ID 101 OF oDlg UPDATE
oGet2:bGotFocus := {|| oGet2:SetColor( 16777215, 128 ) }
oGet2:bLostFocus := {|| oGet2:SetColor( 0, ) }
The Get-Fields inside the Resource, must be sorted to running Numbers.
A Return on a Focused Get, will move to the next one.
Best Regards
Uwe
Since 1995 ( the first release of FW 1.9 )
i work with FW.
If you have any questions about special functions, maybe i can help.
i work with FW.
If you have any questions about special functions, maybe i can help.
Uwe:
I'm not using resources, will it work ? Thank you very much my friend. 
if oDialog:oCtlFocus == oGet[1]
if nKey = VK_RETURN
oGt[1]:oWnd:GoNextCtrl(oGt[1]:hWnd)
end
endEmail: SamirSSabreu@gmail.com
xHarbour 1.2.3 + Fwhh 20.2
xHarbour 1.2.3 + Fwhh 20.2
HunterEC wrote:Guys:
On a dialog with a couple of says & gets, how can I:
1. Highlight in other color the current get ?
Thank you.
Use this function to Highlight color of current get:
SetGetColorFocus( nClrFocus )nClrFocus parameter is optional and defaults to RGB( 235, 235, 145 )
Regards
G. N. Rao.
Hyderabad, India
G. N. Rao.
Hyderabad, India
HunterEC wrote:Guys:
On a dialog with a couple of says & gets, how can I:
2. Move between fields with the ENTER key instead of the TAB key ?
Thank you.
We do not have to write any code for this. By default pressing either ENTER key or TAB key moves to the next field.
Regards
G. N. Rao.
Hyderabad, India
G. N. Rao.
Hyderabad, India
I tested :
SetGetColorFocus( nClrFocus )
the first Time, but why it doesn't work with Multiline-Get ?
Added SetGetColorFocus( 16577214 ) on Top of the Application
That Works with Multiline Get
// ------ Font - Source + Color ----------------------
REDEFINE GET oGet2 VAR SOURCETEXT ID 530 OF oDlg MULTILINE UPDATE
oGet2:bGotFocus := {|| oGet2:SetColor( 0, 16577214 ) }
oGet2:bLostFocus := {|| oGet2:SetColor( 0, ) }
Best Regards
Uwe
SetGetColorFocus( nClrFocus )
the first Time, but why it doesn't work with Multiline-Get ?
Added SetGetColorFocus( 16577214 ) on Top of the Application
That Works with Multiline Get
// ------ Font - Source + Color ----------------------
REDEFINE GET oGet2 VAR SOURCETEXT ID 530 OF oDlg MULTILINE UPDATE
oGet2:bGotFocus := {|| oGet2:SetColor( 0, 16577214 ) }
oGet2:bLostFocus := {|| oGet2:SetColor( 0, ) }
Best Regards
Uwe
Since 1995 ( the first release of FW 1.9 )
i work with FW.
If you have any questions about special functions, maybe i can help.
i work with FW.
If you have any questions about special functions, maybe i can help.
I tested :
SetGetColorFocus( nClrFocus )
the first Time, but why it doesn't work with Multiline-Get ?
SetGetColorFocus( nClrFocus ) is available in FWH from October 2007.
This is intended for normal Gets only, not multi-line gets.
Regards
G. N. Rao.
Hyderabad, India
G. N. Rao.
Hyderabad, India
We do not have to write any code for this. By default pressing either ENTER key or TAB key moves to the next field.
I don't believe this is true. If there is a default pushbutton, then that pushbutton is activated when the Enter key is pressed. This is standard Windows behavior, and I don't think it is a good idea to deviate from this standard. Users expect dialogs to work this way. Using the Enter key for field movement is a holdover from the Clipper apps era and should be abandoned (IMHO).
James
FWH 18.05/xHarbour 1.2.3/BCC7/Windows 10
If there is a default pushbutton, then that pushbutton is activated when the Enter key is pressed.
Yes. But when a dialog and gets are written in source code (not resources) there is no default button unless specifically coded with DEFAULT clause. So, if the programmer wants Enter key to navigate to the next get, he better does not provide for a DEFAULT button.
I don't believe this is true.
But this is true. I presume the FWH code is written that way to accommodate those programmers who insist on the old DOS behavior on windows applications too. The behavior of FWH is that Enter key invokes DEFAULT pushbutton if it is there and otherwise navigates to the next control.
This is standard Windows behavior, and I don't think it is a good idea to deviate from this standard. Users expect dialogs to work this way. Using the Enter key for field movement is a holdover from the Clipper apps era and should be abandoned (IMHO).
While I personally agree with you totally, we see here many programmers who insist on behavior compatible with legacy DOS applications. It is understandable that FWH caters to the needs of all programmers.
Regards
G. N. Rao.
Hyderabad, India
G. N. Rao.
Hyderabad, India
Rao,
I meant that it is not true whenever there is a default pushbutton. And there is a default pushbutton (by default) whenever a new dialog is designed in Workshop. It is extremely tedious to write code for dialogs, so I am not sure why anyone would choose to do that over visually designing them. Perhaps because they do not know that they can visually design them.
James
FWH 18.05/xHarbour 1.2.3/BCC7/Windows 10