I see where you are coming from now. I always think of it as: a group
with background behavior is a shared group that is only placed on one
card. This probably stems from my HC experience, where 1-card
backgrounds are very common.
On 3/1/04 11:08 PM, Dar Scott wrote:
On Monday, March 1, 2004,
On Monday, March 1, 2004, at 09:19 PM, J. Landman Gay wrote:
Note that background behavior is not the same as sharing the group,
that is, placing the group among several cards in the same stack.
How is it different?
A group may be shared among several cards. That is independent of
whether the b
On 3/1/04 7:43 PM, Dar Scott wrote:
Note that background behavior is not the same as sharing the group, that
is, placing the group among several cards in the same stack.
How is it different?
--
Jacqueline Landman Gay | [EMAIL PROTECTED]
HyperActive Software | http://www
omas McGrath III
> Sent: Monday, March 01, 2004 8:21 AM
> To: How to use Revolution
> Subject: Re: Problem with Image on background property
>
>
> What happens if you have a group set to background behavior and then
> put that in a group that does not have background behavior?
On Monday, March 1, 2004, at 07:21 AM, Thomas McGrath III wrote:
What happens if you have a group set to background behavior and then
put that in a group that does not have background behavior?
curious
Tom
I don't know. However, properties can be set unshared even in nested
groups.
My guess:
What happens if you have a group set to background behavior and then
put that in a group that does not have background behavior?
curious
Tom
On Feb 29, 2004, at 7:39 PM, Dar Scott wrote:
On Sunday, February 29, 2004, at 06:51 AM, Stephen King wrote:
Any ideas why each card sees the same image a
On Sunday, February 29, 2004, at 06:51 AM, Stephen King wrote:
Any ideas why each card sees the same image and why the image reference
appears on new generated cards?
I think only field text and button highlight can be shared.
Create an unshared image from a group with a hidden field to contain a
I'm afraid it wasn't clear to me from the docs that images were shared
Steve,
In my experience, an image is shared if it's part of a group with
background behavior set to true, but local if simply placed on a card.
This will also be true of the icon of a button in a background group;
but it's f
Thanks everyone for the very quick replies.
At least ths explains whats happening! The aim is straightforward placing of
the member image in the card as part of the database.
I'll try Robs idea of using a button and if not quite what I want, the
custom property approach seems pretty straightforwa
So for those kinds of objects, a good approach is to store the path to
the image (or selection in a menu button, etc.) in a custom property on
each card, and then on preOpenCard reinstate that path/selection from
the custom property before the card draws.
Steve, et al:
Have you looked at the alter
l: [EMAIL PROTECTED]
Web Site: http://www.sonsothunder.com/
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Stephen King
> Sent: Sunday, February 29, 2004 7:51 AM
> To: [EMAIL PROTECTED]
> Subject: Problem with Image on b
Steve,
Uncheck the background behavior for that group. It is shared on all
card if checked.
If you need a backrgound group and an image then make two one with BG
on and the other with BG off.
HTH
TOm
On Feb 29, 2004, at 8:51 AM, Stephen King wrote:
Hi all,
I'm sure this is really simple, b
Hi Stephen,
Hi all,
I'm sure this is really simple, but I can't understand what is
happening.
I am experimenting with a basic database example and have an image on
the
card as part of the background group. I start with a card with empty
fields
and image (no file reference). I then fill in dat
Hi all,
I'm sure this is really simple, but I can't understand what is happening.
I am experimenting with a basic database example and have an image on the
card as part of the background group. I start with a card with empty fields
and image (no file reference). I then fill in data, reference an
14 matches
Mail list logo
