2 Problems with TSpinEdit

[chrv]

Hi all,

2 problems (see attached)

1/ Why is the NullValue shown at runtime while the value is set to 10 at designtime (and to 20 in FormCreate at runtime) ?
2/ Is it possible to Nullify the TSpinEditEx by code (instead of showine a 0) ?

Thanks all

[Bart]

2/ Is it possible to Nullify the TSpinEditEx by code (instead of showine a 0) ?

You "nullify" the control by settingit's value equal to it's NullValue (which is 0 by default).
If Value = NullValue then the NullValueBehaviour controls what is shown in the control.

Bart

[jamie]

I was going to say something about the version of LAZ 2.0.14 or something like that.

I tested that on 2.0.4 and trunk, it works fine.

[Bart]

1/ Why is the NullValue shown at runtime while the value is set to 10 at designtime (and to 20 in FormCreate at runtime) ?

That is in fact a bug.
Fixed in commit 5168d97f.

Thanks for reporting.
Please test and report back.

Bart

[chrv]

That is in fact a bug.
Fixed in commit 5168d97f.

@Bart : it works now. Thank you so much .

Unfortunately, the other doesn't.
When I set it to NullValue by code with NullValueBehaviour=nvbShowTextHint, in fact it shows "0" (not "MY NULL VALUE" in my case).

[Bart]

It's been a while since I wrote that code.
But NullValue etc. are only supposed to come into play when you clear the control (and then leave it).

Explanation: this control initially was intended to replace the standard TSpinEdit's in the IDE's anchor editor, but that never happened.
Notice that a TSpinEdit cannot have an empty text (when you leave the control), but TSpinEditEx can.

If you clear the Text and then query Value, then, if NullValueBehaviour is set to nvbShowTextHint, it will return NullValue.
Notice that NullValue is allowed to be greater than MaxValue or less then MinValue.

So: if you set Value to NullValue, either by code, or by typing the text or using the spinners, the actual value is supposed to be in the control.
In your case, where NullValue = 0, it must show '0' in the control.
This is both at designtime and at runtime.

So, the previous fix I made is wrong.
After the window is initialized, the control's text is empty.
It then calls UpdateControl, causing the the NullValueBehaviour to take effect.
This should not happen (see explanation above).
It should simply show '0'.

I fixed that in commit a3ba11e5.

Bart