Mountain Lion File Versioning

[J. Landman Gay]

That could happen if the location of the plugin changed, and the stack 
does not have its destroystack property set to true. Without 
destroystack, the stack will stay resident in RAM after closing. If it 
re-opens from a different file path, the engine would think it's a 
duplicate.

If LiveCode was relaunched in between then that wouldn't be the reason.

On 10/11/12 4:16 PM, Peter Haworth wrote:
> Folks,
> I'm really interested in figuring out what happened here so if anyone can
> figure it out, please post!
>
> lcStackBrowser saved a couple of things in custom props between runs but
> I'm already in the process of changing it to save the same info in a file
> to avoid whatever is causing this problem but sure would be nice to know
> what happened.
>
> Pete
> lcSQL Software <http://www.lcsql.com>
>
>
>
> On Thu, Oct 11, 2012 at 11:53 AM, Scott Rossi <scott at tactilemedia.com>wrote:
>
>> Maybe this is one of those situations where the OS is re-launching
>> whatever files you had previously open.
>>
>> Regards,
>>
>> Scott Rossi
>> Creative Director
>> Tactile Media, UX Design
>>
>>
>>
>>
>> On 10/11/12 11:46 AM, "Guglielmo Braguglia" <guglielmo at braguglia.ch>
>> wrote:
>>
>>> I have the problem ...
>>>
>>> I'm using one Peter plugin, lcStackBrowser, which currentlysaves
>>> something inside itself ...
>>>
>>> Today, trying on a MacBook running Mountain Lion 10.8.2, I have had this
>>> strange behavior ...
>>>
>>> ... I opened LiveCode on this machine, on which I had used it a few days
>>> ago, and ... a LiveCode message informs me of a conflict for a duplicate
>>> stack name between two similar stacks !
>>>
>>> One was "lcStackBrowser", another was "lcStackBrowser (Guglielmo's
>>> MacBook)"  :o
>>> Obviously I NEVER created the second one so ... the only thing that I
>>> can imagine is the behavior of Mountain Lion on saving files ...
>>>
>>> Has anyone had a similar experience ?
>>>
>>> Guglielmo
>>>
>>>
>>> On 11.10.2012 19:21, Peter Haworth wrote:
>>>> I'm not 100% clear on how the Mountain Lion file versioning of files
>>>> works
>>>> but does it have any effect on saving a stack by script?
>>>> Pete
>>>> lcSQL Software <http://www.lcsql.com>
>>>> _______________________________________________
>>>> 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
>>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>
>>
>>
>> _______________________________________________
>> 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
>>
> _______________________________________________
> 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
>


-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com