bulia byak wrote:
On 3/20/06, Joshua A. Andler <joshua@...533...> wrote:
One thing has become apparent though, you seem to be against the "auto-grouping" that other apps do. Why is that?
I'm against auto-anything if it does not really do anything which I can't do myself just as easily.
Fair enough.
I definitely understand what you're saying, and can agree that grouping is not too painful. What I needed to communicate in the last email was with the mentioned grouping... clipping "groups" are not quite like regular groups, they have special editing properties. Let me save a whole lot of correspondence by asking a question. Will it be possible to move objects around inside (and out) of the clipped area while clipping is applied? I believe there was a bug that was recently fixed for transforming the clippath with the clipped object. That bug allowed me to do what I speak of and that's really the most important thing that I'd personally need.
For the record, I noticed that I can moved nodes around and do the shape tool adjustments within the clipping area. So if we have a method other than selecting all nodes of an object, that's what I'm looking for.
If by "exponentially" you mean what this word _really_ means, then of course no. It will increase size and probably somewhat affect the performance, but not by much. I don't think the change in performance will be even measurable in 1000 objects using 1 mask vs. 1000 objects using 1000 masks. On the other hand, sharing one mask among several non-grouped objects is sure to have a lot of hidden issues and extra code to guard against surprises.
I trust you, if you really think that the performance difference wouldn't even be measurable then my fears are laid to rest
-Josh.