Field Tabstops oddity (was IDE vs MSG...)

[dunbarx at aol.com]

Richard,


Well, it turns out it is a feature. LC is indeed mixing widths and stops. And the dictionary says it always did: If a tabStop is less than the previous one, it uses that previous as a baseline, essentially making the smaller one a tabWidth, since the baseLine is now locally zero.



So Alejandro's crashes are a mystery.


Craig


-----Original Message-----
From: Richard Gaskin <ambassador at fourthworld.com>
To: use-livecode <use-livecode at lists.runrev.com>
Sent: Wed, Aug 14, 2013 1:54 pm
Subject: Re: Field Tabstops oddity (was IDE vs MSG...)


dunbarx wrote:
> It seems that when an anomalous string for tabStops is set, LC uses a hybrid 
of tabStops and tabWidths.
>
> I have the following tabStops in a table field (named f55"): "20,10,80".
>
> It would appear that the second stop is to the left of the first stop. 
Something similar to this has crashed LC with at least one user. For me, though, 
LC seems to set the first tabStop at 20, then sets a tabWidth of 10, and finally 
the last tabStop at 80.
>
> on mouseUp
>    set the tabstops of fld "f55" to "20,10,80" -- hybrid tabs
>    wait until the mouseclick
>   set the tabwidths of fld "f55" to "20,10,80" --expands to expected values
> end mouseUp
>
> Feature or bug?

I'd say feature, because it's doing exactly what you asked it to do.  If 
you want to set tab widths use the tabWidths property.

--
  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 at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode