On 30 December 2010 23:22, J. Landman Gay wrote:
> On 12/30/10 4:44 PM, David Bovill wrote:
>
> Yes - those use cases are fine. I want to make sure I am not exporting
>> identical information about objects twice, so I want to know which groups
>> in
>> a stack are backgrounds in the shared id s
On 12/30/10 4:44 PM, David Bovill wrote:
Yes - those use cases are fine. I want to make sure I am not exporting
identical information about objects twice, so I want to know which groups in
a stack are backgrounds in the shared id sense - there is no function for
this, so I've had to take a diff
On 30 December 2010 21:24, J. Landman Gay wrote:
>
> You can place any group on a card, regardless of its backgroundBehavior.
> All of the background* functions return only those groups with
> backgroundBehavior set, whether or not the group is placed on the current
> card. It is unusual to assig
On 12/30/10 5:13 AM, David Bovill wrote:
What i did not get is that what is happening
here is such a hack, that is there are two important concepts / behaviors of
backgrounds:
1. It is shared across many cards and changing a property of one changes
the property of all ie they are the sam
Thanks for the replies Andre and Jim!
On 30 December 2010 10:38, André Bisseret wrote:
>
> Look at "backgroundNames" in the doc:
> -
> Comments:
> The backgroundNames is the list of all backgrounds in the stack whose
> backgroundBehavior property is set to true, whether they
Bonjour David,
Look at "backgroundNames" in the doc:
-
Comments:
The backgroundNames is the list of all backgrounds in the stack whose
backgroundBehavior property is set to true, whether they appear on the current
card or not. If a group in the stack contains groups, only th
I don't have a specific answer for this set of questions, but durning
a holiday week few may be available to answer.. so here goes.
I rarely use groups as backgrounds for my projects.
You may be in the land of
synonyms
backward compatible to HCard
oddities of groups
message path pri
OK - it's morning and I still don't get it.
In my simple test stack, I have 3 groups and 3 cards. One of the groups
(group "Inner") is inside another, and both top level groups (group "First
background" and group "Second Nested Background") are on the first card and
the last card, all though they
Now I'm lost...
You can even create backgrounds that are (almost) impossible to detect. If
you create a top level group called "Hidden background" and then "remove" it
from the card - it will appear in the backgroundids / backgroundnames of the
stack even though it is not visible on any cards.
Ho
I thought things were fairly simple - a background is a group with the
background behavior set to true, well at least as long as it is a toplevel
group and not a nested group - this definition works with the way that "the
backgroundids of stack" works.
The thing that throws me is that - what you r
10 matches
Mail list logo
