Empty cards created for script-only stacks - why and is it a problem?
Posted: Fri Jan 28, 2022 3:18 am
A new year, same problems.
I'm still having issues building my projects as standalones if they incorporate script-only stacks. I thought it worked but it only does it sometimes.
So I was wondering if this had anything to do with it.
If I look at the stacks in the Project Browser, they all have cards associated with them. If I delete the cards from the script-only stacks, they reappear when I try to build the stand alone. Livecode also opens these empty cards its just created when I do the build.
I guess Livecode thinks that stacks must have at least one card. But these stacks are scripts being used as behaviours for other cards.
Is this card creation a problem? Is there a way to get rid of them?
Since when I mention the project browser people say "don't use the project browser" then I thought I'd say that I also looked in revApplicationOverview and revNavigator and the empty cards also appear there, but reappear when deleted or cannot be deleted.
I'm still having issues building my projects as standalones if they incorporate script-only stacks. I thought it worked but it only does it sometimes.
So I was wondering if this had anything to do with it.
If I look at the stacks in the Project Browser, they all have cards associated with them. If I delete the cards from the script-only stacks, they reappear when I try to build the stand alone. Livecode also opens these empty cards its just created when I do the build.
I guess Livecode thinks that stacks must have at least one card. But these stacks are scripts being used as behaviours for other cards.
Is this card creation a problem? Is there a way to get rid of them?
Since when I mention the project browser people say "don't use the project browser" then I thought I'd say that I also looked in revApplicationOverview and revNavigator and the empty cards also appear there, but reappear when deleted or cannot be deleted.