Can a script preempt substack name conflicts?

[dunbarx at aol.com]

Hi.


Can you trap "openStack" in a backScript (making sure that any other such message handlers pass it along), to get a list of the already open stack names, along, of course, with the name of the stack of interest, and see if any match?


Craig Newman



-----Original Message-----
From: David Epstein <dfepstein at comcast.net>
To: use-livecode <use-livecode at lists.runrev.com>
Sent: Thu, May 14, 2015 9:17 pm
Subject: Can a script preempt substack name conflicts?


With stack A already open, I open stack B and get a alert like this:

"A stack
"<substackName>" in file <fileName of stack A> is already in memory.  The
Revolution UI does not distinguish stacks which have identical names, so editing
these stack files while both are in memory could result in data loss.”

Is it
possible by script to intercept the message that generates this alert, and
rename either the substack that is already in memory or the substack of the
stack I am trying to open, so as to avoid both the alert and the risk of data
loss?  My impression is that if I try to learn the substack names of a file I
will already be loading that file into memory, and it will be too late to head
off the alert.

Many thanks.

David
Epstein
_______________________________________________
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