Maurilio,
I re-read the message thread and realized you want to use different border colors as indicators.
Still as I pointed out in a previous message, the method Microsoft has started using is coloring the control's background not the border. So you might want to consider doing this instead (and it would not require modification of any of the FW source).
James
Antonio:
Thanks a lot, I'll try it!
James:
The intention is paint the border with a different color to mandatory fields (for example) to let the user have a visual reference.
Using themes under XP we have controls with line border or "flat style" but who don't use themes or Win98 don't have it. The only way I found to use this flat borders and colored references is changing controls for myself.
Best regards,
Maurilio
Maurilio,
>The intention is paint the border with a different color to mandatory fields (for example) to let the user have a visual reference.
That is what the pink field is in the example screenshot in my previous message. I have no mandatory fields as explained in my previous message, I call them critical data, but these are what you would call mandatory. They are pink until filled out, then they become white. Or, they could become yellow if the data is suspect.
As I said, if you make fields mandatory and the user doesn't have the needed data, then they will make something up. (I assume by "mandatory" you mean that they must be filled out before the dialog can be saved.)
>Using themes under XP we have controls with line border or "flat style" but who don't use themes or Win98 don't have it. The only way I found to use this flat borders and colored references is changing controls for myself.
You can use field colors in all versions of Windows, and you don't need to modify the FW source. Also, it works with or without themes.
Regards,
James
This might Tget add more datas to control features, border color, flat style ,underlined style , etc.
Shuming Wang
Hi,
How to disable tget 3D effect or without border ?
redefine get var1 id 101 of odlg
in .rc/dll without WS_BORDER .
EDITTEXT 101, 145, 34, 31, 12
Still with 3D effect .
Thanks !
Shuming Wang
redefine GET oGet VAR var1 id 101 of oDlg
oGet:bPainted = { || PaintBorder( oGet, oDlg ) }
...
function PaintBorder( oGet, oDlg )
local aPoint1 := { -1, -1 }
local aPoint2 := { oGet:nHeight, oGet:nWidth }
aPoint1 = ClientToScreen( oGet:hWnd, aPoint1 )
aPoint1 = ScreenToClient( oDlg:hWnd, aPoint1 )
aPoint2 = ClientToScreen( oGet:hWnd, aPoint2 )
aPoint2 = ScreenToClient( oDlg:hWnd, aPoint2 )
WndBox( oDlg:GetDC(), aPoint1[ 1 ], aPoint1[ 2 ], aPoint2[ 1 ], aPoint2[ 2 ] )
oDlg:ReleaseDC()
return nil
Shuming,
Please try to reduce the dimensions of the rectangle:
local aPoint2 := { oGet:nHeight - 1, oGet:nWidth - 1 }
Antonio,
Is there a way to change oget:nstyle ? so get true no border effect ?
Regards!
Shuming Wang
Shuming,
As far as we know, Windows only allows to use or not a border, but no the type of the border. Thats why we have to paint ours on top of it.
Antonio,
According to MR Wensheng Liao's advice, change .rc/dll EXITTEXT --> user defined control, for example:
EDITTEXT 101, 51, 31, 58, 12
change to
CONTROL "", 101,"EDIT",0 , 51, 31, 58, 12
This can do a no border get , then self add a wndbox()
Regards!
Shuming Wang
EDITTEXT 101, 51, 31, 58, 12
and
CONTROL "", 101,"EDIT",0 , 51, 31, 58, 12
are two different syntaxes for the same control, as far as I know.
EMG
E.M.G,
It seems , Tget class can't Recognizing if .rc/dll EDITTEXT with WS_BORDER clause.
Shuming Wang
