Perhaps this is obvious to everyone but me. I sent a stack (as an app) to a client and used apple messages to share it. The stack relies on a sensible stack path. Everything looked sensible BUT having sent it by messages produced problems and when I made the stack path visible, instead of something sensible like /User/JB/Dropbox/etc it produced some bizarre path for the stack which stopped it from working.
So I sent it by email. Same deal.
So I sent him a dropbox link. Worked fine.
I'm not technical enough to know what was going on. Anyhow, dropbox links are the solution. Hope that helps someone as the forums are always helping me.
Sending stacks to clients - problem
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
-
- Posts: 52
- Joined: Mon Apr 06, 2020 1:19 pm
- Location: Thailand
- Contact:
Re: Sending stacks to clients - problem
Hi bbalmer,
In that case you should definitively ZIP the app and try again, since macOS apps are in fact FOLDERS in disguise!
Best
Klaus
so you create a standalone for macOS?bbalmerTotalFluency wrote: ↑Sat Oct 21, 2023 5:09 amI sent a stack (as an app) to a client and used apple messages to share it.
In that case you should definitively ZIP the app and try again, since macOS apps are in fact FOLDERS in disguise!
Best
Klaus
-
- Livecode Opensource Backer
- Posts: 9444
- Joined: Fri Feb 19, 2010 10:17 am
- Location: Bulgaria
Re: Sending stacks to clients - problem
Or pop it inside a DMG disk image. This the 'Mac way' of despatching apps.