Thanks, that explains it. I've incorporated Trevor's DataView and it has
about 10 stacks in use as behaviors and libraries. To add to the fun, I'd
forgotten that building for mobile no longer disables desktop platforms so
I didn't think to disable them manually, and the standalone builder put up
Jaque,
I’ve seen this when building standalones with stacks that are using library
stacks, and the same library stackflles are included in the standalone build.
Apparently the included stacks are opened during the build process, thus
colliding with the library stacks already in memory. If this
When building a standalone (for mobile in this case) I'm getting repeated messages about stacks
already being in memory and asking me what to do with them. Since I have a lot of included
stacks I need to make a decision a dozen times. This is different from all the "open*"
messages, so that work
