That's exactly what I wanted. :-)
It's handy for small customizations to built-in appearances. I just have to
override what is needed instead of copying the whole entry.
Sebastian Werner wrote:
>
> In 0.7 you need to define it completely. The most users think this is
> more convenient becaus
In 0.7 you need to define it completely. The most users think this is
more convenient because they have the full styling of a widget in one place.
However with the current trunk and finally 0.7.1 you will have the
possibility to add a base:true to include the super class definiton with
lower pr
I have already changed the height in the spinner to 20, but I lose the top
and bottom borders.
I'm investigating why. Very strange.
When extend the Ext appearance, and I want to redefining the 'spinner'
entry.
Should the full entry be redefined or I just can the new height value?
This fails:
No, I think not. Height is quite a functional property. That the widget
comes with a default height is a good choice in this case. If the user
or the appearance theme changes the font one must also correct the
height there. Theme and user values have higher priority than init
values so that is
Hi,
The spinner with the font I have choosed is taller than a combo.
I've seen this in Spinner.js
properties: {
height :
{
refine : true,
init : 22
},
}
Wouldn't be better be its height defined in the appearance?
--
View this message in context:
http://www.nabble.com/
