[Lazarus] TSpinEdit - a modest propoal

[Mattias Gaertner]

On Sat, 15 Jun 2013 22:46:11 +0200
Bart <bartjunk64 at gmail.com> wrote:

> On 6/15/13, Alejandro Gonzalo <parkingspace26 at yahoo.com> wrote:
> 
> > When ReadOnly is True the up/down buttons remain although they don't now do
> > anything.  In that case the number display are should instead occupy the
> > entire component width.
> 
> Why should they?
> I'm not even sure this can be accomplished across widgetsets.

That's not a big problem.
It is only a visual thing. It does not need extra events.
You can implement it only in some interfaces, document it via the
'Restricted' and add a widgetset capability flag, so that applications
know if the current widgetset supports it.

 
> > This way there would be a way to display a number
> > directly without first converting to a string.
> 
> You lost me there.
> Besides a Value property the control also has a Text property.
> But none of this should have anything to do with wether or not the
> up/down arrows are visible.

Yes, I didn't understand that neither. Probably it gets more clear when
seeing the patch.

Mattias