Hi All
I would like to use the line-height: property for a field, but I can’t get it to work. I tried with the units px, em, and %, but neither seems to work. Has anyone successfully used this in a field style. My style (using % in this case) looks like:
field.info
{
font: 11pt LucidaGrande;
color: #333333;
margin: 4px 0px 0px 0px;
line-height: 150%;
}
Regards, Robert
I don’t think that it’s a supported property for fields.
Thanks, Nicola, do you know of any other style property to control the space between lines?
ngervasi:
I don’t think that it’s a supported property for fields.
If you mean the spacing between two lines of text inside a text area field, no, really no. Sorry.
I guess you can file a feature request for this.
Yes, I mean exactly that, it’ a pity but that’s how it seems to be. BTW, is there somewhere a reference which styles are currently supported?
ngervasi:
If you mean the spacing between two lines of text inside a text area field, no, really no. Sorry.
I did file a feature request, Robert
Regards, Robert
ROCLASI:
I guess you can file a feature request for this.
Robert Huber:
Yes, I mean exactly that, it’ a pity but that’s how it seems to be. BTW, is there somewhere a reference which styles are currently supported?ngervasi:
If you mean the spacing between two lines of text inside a text area field, no, really no. Sorry.
Servoy “styles” are definitely confusing for a number of reasons. The main one being that it takes time to figure out what works and what doesn’t as changes can only be done at design time. If you could make style changes at runtime then we would have had a demo application out a long time ago showing the effects of style changes on all types of objects.
Second, styles can have slightly different effects on different platforms. But this isn’t the style’s fault – properties in general are different on different platforms. Loading in a different style sheet at startup that is designed for the target platform is one of the advantages of styles. But it does mean that you have to test various style combinations out on more than one platform – adding to the amount of grunt work.
Last, styles don’t cascade. It would be nice to have solution and form scoped styles – with the form scope style overriding/adding to the global style setting. Currently, if you want a form to look a bit different than other forms you have to switch out the entire style sheet. This leads to multiple style sheets with sometimes very minor variations between them. Keeping them all current is tricky – which happens more than you think with each new operating system and java update that comes out.
Styles are meant to make life easier and they do to a degree. But they sure are a pain in the ass on a lot of levels and they haven’t been improved upon much since the day they were implemented several Servoy versions ago. Not sure if Servoy 5 has any style improvements – still working through the long list of stuff they brought out!
Hi David
david:
]Servoy “styles” are definitely confusing for a number of reasons. The main one being that it takes time to figure out what works and what doesn’t as changes can only be done at design time. If you could make style changes at runtime then we would have had a demo application out a long time ago showing the effects of style changes on all types of objects.
I agree with you, and style changes at runtime would be very very helpful.
david:
Second, styles can have slightly different effects on different platforms. But this isn’t the style’s fault – properties in general are different on different platforms. Loading in a different style sheet at startup that is designed for the target platform is one of the advantages of styles. But it does mean that you have to test various style combinations out on more than one platform – adding to the amount of grunt work.
To support you, we also have spent too much work in this to get acceptable results, and the bad thing is it’s more or less what I call useless know-how
david:
Last, styles don’t cascade. It would be nice to have solution and form scoped styles – with the form scope style overriding/adding to the global style setting. Currently, if you want a form to look a bit different than other forms you have to switch out the entire style sheet. This leads to multiple style sheets with sometimes very minor variations between them. Keeping them all current is tricky – which happens more than you think with each new operating system and java update that comes out.
Hey, I many times wished for styles to cascade, but huchhh, no luck till now.
david:
Styles are meant to make life easier and they do to a degree. But they sure are a pain in the ass on a lot of levels and they haven’t been improved upon much since the day they were implemented several Servoy versions ago. Not sure if Servoy 5 has any style improvements – still working through the long list of stuff they brought out!
Can’t add anything more …
Regards, Robert
PS: BTW, I did not find anything about styles in the new Wiki Doku, did I not find it?
“useless know-how” …that about sums it up completely right there
I would like I could put a smile on … may be one Servoy day in the future
david:
“useless know-how” …that about sums it up completely right there