S
SteveM
I have a set of small images colored white with transparent
backgrounds. I want to overlay them on copies of a master square with
a shapesheet that has been augmented with Smart Tags and Actions. I
would like to group or "fuse" the two shapes together without losing
the shapesheet structure of the parent square.
However If I just group the shapes together, the square shapesheet
info is embedded inside the group, hiding activation of the square
Smart Tags. I tried converting the square to its own group and using
Add to Group with the image. That technique maintains visibility of
the square shapesheet actions to the mouse, but the grouped image is
buried under the colored square and will not surface using the Bring
Forward command.
So how do I do that? How do I combine two shapes and keep them
visible while maintaining the shapesheet information of one of them?
I'm sure I'm missing something fundamental on how to do this. And I'm
guessing this is part of a more formalized design process for
constructing shape libraries. I.e. sequencing the order of
construction events to minimize rework.
Any help or reference suggestions would be really appreciated.
Thanks Much,
SteveM
backgrounds. I want to overlay them on copies of a master square with
a shapesheet that has been augmented with Smart Tags and Actions. I
would like to group or "fuse" the two shapes together without losing
the shapesheet structure of the parent square.
However If I just group the shapes together, the square shapesheet
info is embedded inside the group, hiding activation of the square
Smart Tags. I tried converting the square to its own group and using
Add to Group with the image. That technique maintains visibility of
the square shapesheet actions to the mouse, but the grouped image is
buried under the colored square and will not surface using the Bring
Forward command.
So how do I do that? How do I combine two shapes and keep them
visible while maintaining the shapesheet information of one of them?
I'm sure I'm missing something fundamental on how to do this. And I'm
guessing this is part of a more formalized design process for
constructing shape libraries. I.e. sequencing the order of
construction events to minimize rework.
Any help or reference suggestions would be really appreciated.
Thanks Much,
SteveM