Grouping inside Grouping not that robust

Sivakatirswami katir at hindu.org
Sun Mar 12 04:19:15 EST 2006


Yes, this can become a bit of a challenge  to say the least.  
Especially if you are also trying to get certain objects in some  
groups to be at the top of the group.

Does anyone else wish there were another "group-layer" editing  
strategy in Rev? as we have in photoshop? Imagine a palette which  
only shows  groups. the default "layer" being the ungrouped objects  
on the "bottom" of the card. Groups appear as layers in this palette,  
and you could turn them  on and off move them up and down by  
dragging. if you have a group selected in this palette, all object of  
all groups and as well as the ungrouped  objects of the "default"  
layer, show on screen, but effectively you are editing only objects  
in that group and all other objects in other  groups are  
unselectable, but visible. yet, you could take a selected object and   
drag it from one  group to  another. And the object changes groups.  
The Adobe model for this is close to perfect. I don't know if this is  
one of those things that could be easily translated into the Rev  
core...of if advance Rev usages of groups has some other  constraint  
that makes  such a model unfit,  or if  it  would be some kind of  
major re-engineering effort.  I'm not sure I understand  how having  
groups inside  of groups is even useful, true  it is possible, but  
what if every group were completely independent... would we lose   
something? I suppose  the ability to place several groups all at  
once, by placing a single group has  some utility?  this whole area  
definitely needs a new paradigm or at least a pair of nickels... some  
kind of upgrade.



On Mar 11, 2006, at 2:11 PM, Stephen Barncard wrote:

> It seem like Rev is still got problems with groups inside  
> groups...anyone else seen this?
>
> I've been trying to make design elements out of little line  
> segments, and that requires making groups of groups sometimes to  
> make them movable and usable.
>
> But it's like walking on eggs. Rev gets confused as to what group  
> is what, groups are hard to select, and twice in my case while  
> trying to group it did something horrible to the stack - it made a  
> tabbed button beneath it invisible - like the object shows up in  
> the inspectors, but .... isn't there, isn't offscreen... it's just  
> not visible and no property change will bring it back. Revert.
>
> I think this is a bug and it seems to corrupt the stack.
>
> I guess the rule is -- don't go more than 2 level deep with groups  
> in groups. And as far as graphics go - if I have to work with small  
> pieces, I think I'll do it in Appleworks or MacDraft and assemble  
> the artwork there in front of an image of where they'll go... I've  
> spent hours with this...
>
> It would also be nice if there was some way to know what level of  
> grouping one is in... as well as some way of grouping line elements  
> so that they become a new graphic object.  Or how about 'locking'  
> groups so the elements stays together in the group.




More information about the Use-livecode mailing list