Re can?t save Standalone

2017-12-11 Thread Hillen Richard via use-livecode
Hello, 

thank you for your helpfull answers.

-> Richard Gaskin: syserr is 2, wrong adress

-> Mike Bonner: Standalone tries to save the datastack in folder Contents/MacOS 
of the App-Package; I changed the folder to Resources/_MacOS and it worked ok.

Richard H.
___
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



Re: can´t save Standalone

2017-12-09 Thread Richard Gaskin via use-livecode

Hillen Richard wrote:

> Using this proved datastack-method in the development environment,
> it´s ok;
> But after making a new standalone with "substacks moved in separate
> stackfiles" if I press the Save-button in stack Data I get "can´t open
> stack backup file".

With most commands which may fail for a wide range of reasons, it's 
essential to check "the result" immediately after the command.  For all 
I/O it's especially helpful to include a call to the sysError function 
so you can learn the specific error code the OS is delivering to LC.


e.g.:


  save stack "SomeStack"
  if the result is not empty then
answer the result &" ("& sysError() &")"
exit to top
  end if


--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://www.FourthWorld.com

___
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

Re: can´t save Standalone

2017-12-09 Thread Mike Bonner via use-livecode
Since you already have checked the box to move substacks to separate files,
chances are that it is either a ) Saving the file as a name that is
different than the one you are using in your "open stack ..." command, or b
) its looking in the wrong place.  when you build the standalone, you can
look in the app package and visually check to see how it is being named
(right click the .app, view package contents.)  Or of course you can add a
field to your app and add code to the splash stack that will -- put the
files into field "whateverfieldyouadded" and it will tell you what files
are available in the location that the defaultfolder is set to. (you could
also have it -- answer the defaultfolder to see where its looking for files.
Of the 2 options, a or b, my guess would be A unless livecode has change
the location where it places the separated out stackfiles. (which would be
option b..)  you can poke around in the app package file and determine what
the name of the stack file is, and where its located and then adjust your
code from there.



On Sat, Dec 9, 2017 at 10:10 AM, Hillen Richard via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Hello,
>
> There is - in splash screen method - a very simple stack Main with a
> substack Data, used since 2007.
> Stack Main opens stack Data. In stack Data there is a button "Save" with
> script
>
> "save this stack
> if the result is not empty then answer the result"
>
> Using this proved datastack-method in the development environment, it´s ok;
> But after making a new standalone with "substacks moved in separate
> stackfiles" if I press the Save-button in stack Data I get "can´t open
> stack backup file".
>
> So I cant´t save changed data.
>
> I have built the stack from button up again with the actual LC-Version,
> but same Error.
> Is there any help outside?
>
> Thank you for your helpful hints ,
> Richard.
>
> (macOS 10.13.2, Livecode 8.1.8 Community Edition)
>
>
> ___
> 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
___
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