Still cannot make standalone in v8

[dunbarx]

Still can not use v8.0

I saved two separate stacks. No functionality in either. Call one a "splash" stack. Tried to make a standalone, with one stack added as a stack file to the splash.

I could not add the stackFile to the "splash" stack in the standalone settings. If I try to make the standalone anyway, I get a long list of errors.

I am in OS 10.9. Is that the issue?

Craig Newman

[FourthWorld]

Does the problem persist in the current version, 8.1?

[dunbarx]

Richard.

Sorry, I was sloppy, generic 8. I was in fact in 8.1.

Also, sloppy again. I could NOT add the other stack file to the "splash" in the standalone settings.

I should also have mentioned that the single word "staqck" is the only one listed in the "Stack files in the Applicaion" field, and nothing will add to it. In v6, the actual name of the standalone stack is listed first. It is the one that cannot be deleted.

Craig

[LiveCode_Panos]

Hi dunbarx,

This is reported under bug http://quality.livecode.com/show_bug.cgi?id=18429, and it is fixed in LC 8.1.1 RC-1.

In this report there is a description of the fix which can be applied locally to 8.1.0, in case you don't want to use 8.1.1 RC1 yet.

Best,
Panos
--

[dunbarx]

Panos.

Thanks for the reply. But one question. Am I the only one using v8.1 that noticed this?

Regards,

Craig

[Klaus]

I have built a standalone with LC 8.1 but did not encounter this error!?

[LiveCode_Panos]

Hi Craig,

This bug happens only if the standalone contains multiple stacks, so I guess that Klaus and others that don't see this bug are using a single stack

Best,
Panos
--

[dunbarx]

Panos, Klaus.

No splash stack? You are always writing to external files to save data? No matter, as long as it is fixed.

I am amazed, though, since I always want to save the state of my "working" stacks in a standalone.

Craig

[Klaus]

Hi Craig,

my standalone constists of a single stack and the "editable/saveable" stack is in a custom property
that I "spit out" into the users documents folder if neccessary.


Best

Klaus

[jmburnod]

Hi All,
Tested with LC 8.1.0, OS X 10.10.3
Compilation of a single big stack (34 cps, 20'000 lines scripts) without error
Compilation with the same big stack and one substack without error
(just compilation, I have to test deeper the app, but the first open was a success and that makes me happy)
Compilation with the same big stack and one stack file with the same error
@Craig
Congratulation you are a precious tracker
Best regards
Jean-Marc

[dunbarx]

Klaus.

You know, I have read about the fact that one can store just about anything in a custom property. But how do you store a stack? Do you mean you store the pathName to an existing stack?

In other words, how do you

Code: Select all

get the storedStack of this stack

Craig

[Klaus]

Hi Craig,

nope, I actually put the complete BINfile into a CP!

Read in:
...
set the cStack of this stack to url("binfile:/Applications/Livecode/YTR.livecode")
...
spit out:
...
put the cStack of this stack into url("binfile:/Applications/Livecode/Copy of YTR.livecode")
...

Or even (no file on disk!):
...
put the cStack of this stack into tStackToGo
go stack tStackToGo
...


Best

Klaus

[dunbarx]

Ah, binary data.

Cool.

So you can indeed store a stack in a CP, and regenerate it as required.

Cool.

Craig

[capellan]

Using Custom Properties, the user could store objects or groups (groups that contains images, vector graphics, buttons, text fields, etc.) for reuse in other stacks.

For example, to store a single object or a group inside a custom property, of a stack named "myStorageStack", select the object (or group) and run this script in the message box:

copy the selobj;set the cpData01 of stack "myStorageStack" to the clipboarddata[objects]

To paste this object in a new stack named "myNewStack", use a script like this:

set the clipboarddata[objects] to the cpData01 of stack "myStorageStack";go card 5 of stack "myNewStack";paste