On 3/24/12 8:11 PM, dunb...@aol.com wrote:
I am aware of the ease in which one can accidentally change the name
of a stack in the inspector when you think you are typing somewhere
else. This is a bit insidious. But this was the pulldown to set the
mainstack. Though this property is settable by c
ure I shouldn't leave well enough alone, though.
Craig
-Original Message-
From: Richard Gaskin
To: use-livecode
Sent: Fri, Mar 23, 2012 10:47 pm
Subject: Re: Source of corruption
dunbarx wrote:
> I had posted earlier about a stack I use that became neurotic. If launched in
On 3/23/12 7:26 PM, dunb...@aol.com wrote:
It turns out that the stack had inexplicably had its mainstack
reference changed to another stack. Resetting this back to itself
(there is only one stack in the file) seems to have fixed everything.
Anyone have any experience with this sort of thing?
dunbarx wrote:
> I had posted earlier about a stack I use that became neurotic. If launched in
> a new session from the finder, no problem. But if closed,
> it could not be reopened in the same session. The "stacks" showed no
> reference to it at all soemtimes, though at other times it was
> ind
I had posted earlier about a stack I use that became neurotic. If launched in a
new session from the finder, no problem. But if closed,
it could not be reopened in the same session. The "stacks" showed no reference
to it at all soemtimes, though at other times it was
indeed listed, albeit still
