That makes sense. I was complaining about formattedHeight for fields. For buttons it seems useful.
On Wed, Feb 8, 2012 at 2:26 PM, Bob Sneidar <b...@twft.com> wrote: > One thing I use it for is programmatically setting the height of menu > buttons. I find the default size to be too large for a busy form, so I set > the height to the formattedHeight of the text of the button. I have a > utility that "drops" a field, button or menu onto a card and links it to a > SQL column in a table that the card is linked to. > > Bob > > > On Feb 8, 2012, at 1:26 PM, Howard Bornstein wrote: > > > Given this, the only value I can see for formattedHeight is that it > > guarantees that the field will provide "sufficient" room to display the > > type. That's about it. And even that breaks down with large type sizes > and > > small margins. > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > -- Regards, Howard Bornstein ----------------------- www.designeq.com _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode