Multiple revCursors stacks

Hershel Fisch hershrev at
Thu Aug 12 15:59:35 EDT 2010

I also realize that I have two "revHelpPopup" substacks, under the
revDocumentation stack and under the "revMenuBar" stack, which one has to be
deleted and which one is the correct one. I see it since version 3.504 dp-4.
Prior to the above version its only urder the revMenuBar?
It effects when you press the "restore development tool" btn.

Thanks, Hershel

On 8/12/10 3:20 PM, "Hershel Fisch" <hershrev at> wrote:

> Thanks a mill. Working beautifully.
> Hershel
> On 8/11/10 8:47 PM, "J. Landman Gay" <jacque at> wrote:
>> On 8/11/10 3:12 PM, Hershel Fisch wrote:
>>> Hi and thanks,
>>> Sorry didn't express myself properly, so I'll try to elaborate a bit,
>>> When I open RunRev everything sounds fine, I then open my App. A message
>>> comes up saying "A stack "revMacCursors" 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." with an "ok" btn.
>>> I hit "ok" the app. Opens up, then I go to the application browser I see
>>> multiple substacks of "revCursors" and multi mainStacks of "revMacCursors".
>>> Now, which one do I delete, Since there is no date on them?
>> It sounds like your stack has the cursor stacks embedded in it as
>> substacks, which conflict with those already in the IDE. But check to
>> make sure:
>> In the Finder (or Windows Explorer if you're on a PC) look in Rev's main
>> program folder, in a subfolder called Toolset. See if there are two
>> copies of revCursors and revMacCursors in there. If so, that's where you
>> can compare dates and delete the oldest two. If not, then the IDE is
>> fine. It probably is.
>> In Rev's application browser, open the problem stack and look at its
>> substacks. You should see the cursor stacks in there as substacks of
>> your own stack. Delete them both. Your own stack should not include any
>> cursor stacks. If you need the cursors in a standalone, just assign them
>> in Standalone Settings instead.
>> Save your stack and reopen it. The error should be gone.
> _______________________________________________
> use-revolution mailing list
> use-revolution at
> Please visit this url to subscribe, unsubscribe and manage your subscription
> preferences:

More information about the Use-livecode mailing list