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 "revCu
023, at 2:28 PM, Paul Dupuis via use-livecode
>> wrote:
>>
>> 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
>&
not to confuse the
delete command.
Neville
> On 7 Jul 2023, at 2:00 am, use-livecode-requ...@lists.runrev.com wrote:
>
> A stack "revCursors" is already in memory.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Pleas
>>> 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 ne
"revCursors" is already in memory. The Livecode UI does not
... etc..
Can someone advise what I need to do to address this? I seem to
recall this problem has been seen before.
I think it happens when you include cursors in a standalone build.
Sometimes LC adds it to your stack as well
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 n
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 ad
