The last keyword will always reference the group with the highest
layer. So if you have nested groups this might fail, or if you set the
layer property of the group of course.
Hth,
Malte
___
use-revolution mailing list
Malte.
No. Believe me, I wish it did.
Layers and numbers are scrambled. At least one other person concurs. No
nested groups. No errant settings.
If I group, in succession, five objects, the resulting numbers of the five
new groups are not 1,2,3,4,5, but rather, (let me look at my latest run)
Scott.
Thanks. Not only is the templateWhatEver cool in its own right, and yet
another tool I was not aware of, it makes a workaround a snap.
But this is a bug, I think.
Craig
In a message dated 5/21/09 8:31:39 PM, sc...@tactilemedia.com writes:
Yeah, apparently referencing the last group
Yeah, apparently referencing the last group is still not reliable. If you
need to use this approach in your scripts, one option is to name the
templateGroup, rather than using last, as mentioned here:
http://www.nabble.com/Re%3A-am-I-right-with-select-and-group--p10972065.html
If you can
I have four fields, F1, F2, F3, and F4. Fresh, empty stack.
I wrote a script that groups each field in order, one field to a group,
thinking that the 'last group would always be just that, the latest one
created.
But not so. I came across this because trying to get the last group as I
went
Recently, dunb...@aol.com wrote:
I wrote a script that groups each field in order, one field to a group,
thinking that the 'last group would always be just that, the latest one
created.
But not so. I came across this because trying to get the last group as I
went along always failed.
