On Jun 16, 2015, at 3:46 AM, Tiemo Hollmann TB <toolb...@kestner.de> wrote:
> Hi Devin, > thank you for your explanations. > Either if I am using *go stack "mainStack.rev"*, or using the explicite path > *go stack item 1 to -2 of the effective filename of this stack & slash & > "mainStack.rev"* > Whatever I do, my standalone always prefers the mainStack.rev from the > bundle directory and ignores the given path inside the bundle. Only if there > is no file "mainStack.rev" at the bundle level, the standalone takes the > "mainStack.rev" from inside the bundle. > Though there must be some more straight forward approach, the only solution > I now see is using two different names of the "mainStack.rev", one > "mainStackOSX.rev" for OS X inside the bundle and one "mainStackWin.rev" at > bundle level for the windows version, so that my OS X standalone can't catch > the wrong stack at bundle level anymore. > Thanks Could you create an alias (or dynamic link) from the bundle to the app directory? I don’t know if that would be any advantage, but at least you wouldn’t have to include two different copies of the mainstack. Beyond that, this seems like a bug to me (LiveCode recently changed the way they look for files in Mac .app bundles, and this may have been an unintended consequence.) It might be worth a bug report. Devin Devin Asay Office of Digital Humanities Brigham Young University _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
