Paul
Are you launching a stack that has previously been made into a standalone?
Some time ago very often when I created a standalone it added copies of the
built-in revCursors stack(s) as substacks of my stack. Before I noticed this
subsequent standalone builds could add multiple copies all wi
Well…..
What happens is that when you build an app, every stack it uses will be opened
in the IDE, ostensibly to determine what inclusions are necessary. I have seen
where the version of the stack that is open AFTER building the standalone is
the one in the STANDALONE! So if you continue to us
On 7/6/2023 5:12 PM, J. Landman Gay via use-livecode wrote:
On 7/6/23 9:26 AM, Paul Dupuis via use-livecode wrote:
I have a new Livecode 9.6.9 install on a new Windows 11 laptop. It
was working normally for a while, and, now, whenever I launch it, I
get a warning message:
A stack "revCursors
On 7/6/23 9:26 AM, Paul Dupuis via use-livecode wrote:
I have a new Livecode 9.6.9 install on a new Windows 11 laptop. It was working normally for a
while, and, now, whenever I launch it, I get a warning message:
A stack "revCursors" is already in memory. The Livecode UI does not ... etc..
Ca
I have a new Livecode 9.6.9 install on a new Windows 11 laptop. It was
working normally for a while, and, now, whenever I launch it, I get a
warning message:
A stack "revCursors" is already in memory. The Livecode UI does not ...
etc..
Can someone advise what I need to do to address this? I
