Mainstack contains itself

[montymay]

Running LC 9.5 Business and Windows 10. I have a mainstack consisting of many cards but also containing substacks. Recently I noticed in the Project Browser that there is listed a substack having the same name as the mainstack! Opening that substack reveals a repetition of the cards of the mainstack and its substacks. Opening the second recursion repeats the behavior. (Infinite recursion here?) Below is a screenshot of the Project Browser as it appears upon first opening it. The substack appears three or so rows from the bottom.

How do I delete the substack? (Less importantly, how could this have happened?) RIght clicking the unwanted substack reveals a delete item, but it does not remove it.

Tried building a standalone but I get a error that is discussed in the following thread:
posting.php?mode=reply&f=8&t=29395
Also below is a screenshot of the error dialog:


This unwanted repetition of the mainstack as a substack of itself may be the problem.

Thank you for any suggestions.

Monty

[richmond62]

Well: infinite recursion or infinite cloning of the mainstack into itself?

I would suppose you can discount the latter because
your computer would be well on the way to some sort of memory shortage.

I would suggest,as a first call, you look at your stack with the Application Overview stack:
-

-
This should at least give you an idea as to whether it is a fault inside the stack itself, or just
a fault with the Project Browser (something I NEVER use, having always favoured the Application Overview).

[richmond62]

Should this problem be NOT just a fault of the Project Browser I would do the following:

Save all the substacks into a folder as main stacks (i.e. detach them from your main stack),
the save your main stack.

Then reopen the main stack and see what the Project Browser or App Overview show.

If, as I suspect, the main stack now has NO substacks, reimport your 'normal' substacks
as substacks and save the thing.

That may just sort your problem out.

[FourthWorld]

I'm most interested in how it got this way. Was there any point while you were working that you say a warning about duplicate stack names?

To remedy this might work.(I say "might" only because I've never seen this circumstance before):

1. Make a backup of your file. If anything goes wrong, don't call me.

2. In the Message Box run:

Code: Select all

lock messages; delete stack "db10" of stack "db10"

Let us know how that goes.

[richmond62]

It would be interesting to see if this condition can be duplicated.