arie van der ent
arietext at mac.com
Sat Jan 8 14:34:39 EST 2005
I used your recipe. It works. A question: what the heck is the
difference between compiling a standalone and adding Dreamcard-player
to your stack(s)?
Arie van der Ent
Op 8-jan-05 om 19:15 heeft Marian Petrides het volgende geschreven:
> Ok. I finally got a chance to actually try this out and can confirm my
> original statement, namely that having a group which is set to
> background = true does not interfere with creating a standalone. I'm
> not sure what the problem with your stack is, but it isn't the
> background group.
> Here's what I did, in case you want to try it out yourself:
> Created new mainstack
> On first card, added 2 buttons and a field, grouped them and set
> behave as background to true (using object inspector on the group and
> checking the use as background check box).
> Created 2 new cards. The group, as expected, showed up on both cards.
> I then chose Save As Standalone from the file menu.
> The resulting standalone executes just fine in Mac OSX. HTH.
> On Jan 8, 2005, at 7:04 AM, Marian Petrides wrote:
>> I don't think the behavior you describe is the way it should work
>> (i.e. grouping a bunch of buttons, setting them to behave like
>> background = true and then trying to make a standalone should work in
>> my recollection. Alas, I don't have time to create a simple test
>> stack to verify this right now. Anyone else?
>> However, the reason I am writing now is that I have a viable solution
>> for you, one I know works because I use it all the time and have used
>> it to create a very large interactive casebook.
>> But what I do, that I KNOW works, is:
>> Create splash stack (a hub of sorts) containing a single "title page"
>> card and make into standalone. This splash stack has buttons on it
>> that take you to appropriate cards in one or more OTHER stacks which
>> are NOT standalone.
>> For example: Splash stack has 3 buttons:
>> Button 1; Instructions. Goes to Instructions Stack (not standalone)
>> Button 2: Cases. Goes to Cases Stack (not standalone)
>> Button 3: Quit. Simply quits.
>> In reality, if your stacks are small enough you could even combine
>> the two stacks into a simple "Cases" stack. Then have Button 1 go to
>> cd 1 of stack "Cases" and, assuming your instructions are all on one
>> card, have Button 2 go to cd 2 of stack "Cases"
>> On Jan 8, 2005, at 5:32 AM, arie van der ent wrote:
>>> I am new to Revolution. I understand the concept of building a
>>> standalone. So I made a splash screen as mainstack and put the the
>>> logic in a substack. Building a standalone causes an error. I have
>>> tried to track what causes the error. One of the things I found is
>>> that when I am grouping the elements on a card and set the property
>>> 'behave like a background' to true, it is not possible to a build a
>>> standalone. This can't be true, I think. Is there a solution?
>>> Arie van der Ent
>>> use-revolution mailing list
>>> use-revolution at lists.runrev.com
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
> use-revolution mailing list
> use-revolution at lists.runrev.com
More information about the Use-livecode