dunbarx wrote:
Richard.
..."FWIW, LC recently introduced a new property, the tabWidths, which will
accept those values."
Are you implying that the tabStop list that Alejandro posted is somehow not
acceptable?
I have to admit that I've had so much going on in my office that I
haven't followed this discussion in detail.
But I suspect that the problem stems from a feature in the IDE which may
not have complete error-checking.
The tabstops property requires absolute metrics from the left edge of
the control; that is, each item is the complete measure from that edge,
e.g.:
100,150,225
Recognizing how onerous this can be, RunRev recently added the tabwidths
property to allow us to specify only the widths, without having to add
up the widths for each value, e.g.:
100,50,75
Perhaps the IDE team recognize this onerousness long before the engine
team had a chance to address it with the new tabWidths property, and
wrote the Inspector in a way that effectively allows you to enter what
we now call tabWidths when setting the tabStops, translating them into
true tabStop values when the property is actually set in the control.
If that hunch is correct, perhaps certain sequences of values trip up
that scripted translation, causing the errant behavior noted.
--
Richard Gaskin
Fourth World
LiveCode training and consulting: http://www.fourthworld.com
Webzine for LiveCode developers: http://www.LiveCodeJournal.com
Follow me on Twitter: http://twitter.com/FourthWorldSys
_______________________________________________
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
