To our development team,
Please considere note these my recomendations are not really bug, see it as improvements for our source codes in HMG.
I'm making some tests at: TextBox, ComboBox, EditBox, CheckBox and DatePicker. And I found a error compiling when there is a missing parameter by calling functions directly. IMHO, these errors, should be treated in order to avoid error compiling, as follows:
_DefineTextBox at h_textbox.prg:
DEFAULT invisible TO .f.
DEFAULT RIGHT TO .f.
DEFAULT readonly TO .f.
DEFAULT notabstop TO .f.
DEFAULT bold TO .f.
DEFAULT italic TO .f.
DEFAULT underline TO .f.
DEFAULT strikeout TO .f.
DEFAULT disabledbackcolor TO .f.
DEFAULT disabledfontcolor TO .f.
_DefineMaskedTextbox.prg:
DEFAULT invisible TO .f.
DEFAULT RightAlign TO .f. (not used, but is defined as argument)
DEFAULT readonly TO .f.
DEFAULT notabstop TO .f.
DEFAULT bold TO .f.
DEFAULT italic TO .f.
DEFAULT underline TO .f.
DEFAULT strikeout TO .f.
DEFAULT disabledbackcolor TO .f.
DEFAULT disabledfontcolor TO .f.
Sometimes, it's easier to define control by calling respective function directly, not by DEFINE... or @ ...
IMHO, we have to preserve three ways for controls defining. It's by this reason, I kindly ask to our development team if is posible to be applied. Is it posible ?
Default values at Controls
Moderator: Rathinagiri
- Pablo César
- Posts: 4059
- Joined: Wed Sep 08, 2010 1:18 pm
- Location: Curitiba - Brasil
Default values at Controls
HMGing a better world
"Matter tells space how to curve, space tells matter how to move."
Albert Einstein
"Matter tells space how to curve, space tells matter how to move."
Albert Einstein
Re: Default values at Controls
I agree.Sometimes, it's easier to define control by calling respective function directly, not by DEFINE... or @ ...
It's also be useful to print data, when you can't change right, left aor center justify.
Functions are more useful, especially, when your app has controls definitions stored in database and they are created at runtime.
- Pablo César
- Posts: 4059
- Joined: Wed Sep 08, 2010 1:18 pm
- Location: Curitiba - Brasil
Default values at Controls
For GRID are missing default values at _DefineGrid for:
multiselect
InplaceEditOption
multiselect
InplaceEditOption
HMGing a better world
"Matter tells space how to curve, space tells matter how to move."
Albert Einstein
"Matter tells space how to curve, space tells matter how to move."
Albert Einstein
- srvet_claudio
- Posts: 2220
- Joined: Thu Feb 25, 2010 8:43 pm
- Location: Uruguay
- Contact:
Re: Default values at Controls
Pablo César wrote: _DefineTextBox at h_textbox.prg:
DEFAULT invisible TO .f.
DEFAULT RIGHT TO .f.
DEFAULT readonly TO .f.
DEFAULT notabstop TO .f.
DEFAULT bold TO .f.
DEFAULT italic TO .f.
DEFAULT underline TO .f.
DEFAULT strikeout TO .f.
DEFAULT disabledbackcolor TO .f.
DEFAULT disabledfontcolor TO .f.
_DefineMaskedTextbox.prg:
DEFAULT invisible TO .f.
DEFAULT RightAlign TO .f. (not used, but is defined as argument)
DEFAULT readonly TO .f.
DEFAULT notabstop TO .f.
DEFAULT bold TO .f.
DEFAULT italic TO .f.
DEFAULT underline TO .f.
DEFAULT strikeout TO .f.
DEFAULT disabledbackcolor TO .f.
DEFAULT disabledfontcolor TO .f.
Done!Pablo César wrote:For GRID are missing default values at _DefineGrid for:
multiselect
InplaceEditOption
- Pablo César
- Posts: 4059
- Joined: Wed Sep 08, 2010 1:18 pm
- Location: Curitiba - Brasil
Default values at Controls
Thank you Claudio ! 

HMGing a better world
"Matter tells space how to curve, space tells matter how to move."
Albert Einstein
"Matter tells space how to curve, space tells matter how to move."
Albert Einstein