removing accumulated garbage fro stacks?
pete at lcsql.com
Wed Feb 4 20:40:06 EST 2015
Not sure what might cause that. I would create a brand new stack and put
the script in it, using the name of your mainstack and its substacks
property to get the stack names for the check.
lcSQL Software <http://www.lcsql.com>
Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and
On Wed, Feb 4, 2015 at 4:48 PM, Dr. Hawkins <dochawk at gmail.com> wrote:
> On Wed, Feb 4, 2015 at 4:01 PM, Peter Haworth <pete at lcsql.com> wrote:
> > As mentioned in that thread, there's an undocumented stack property
> > revUnplacedGroupIDs. You'll need a simple script to go through your
> > stack/substacks and check that property.
> I managed to miss that splinter of the thread :(
> Tried it.
> Lots of them.
> 212 in the first stack I checked.
> I tried a button with the script,
> on mouseUp
> repeat with i = 1 to 21
> put the the name of stack i & cr & the number of lines in (the
> revUnplacedGroupIDs of stack i)
> repeat for each line theLin in the revUnplacedGroupIDs of stack i
> put the long name of group id theLin of stack i & cr & the locked
> of of group id theLin of stack i
> end repeat
> end repeat
> end mouseUp
> but I get button "Button": execution error at line n/a (Object: stack
> locked, or object's script is executing)
> But the object is in stack dna, while the button is on stack mcp, and the
> check shows that the group is unlocked
> Dr. Richard E. Hawkins, Esq.
> (702) 508-8462
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the Use-livecode