Inadvertent objects added to Groups
-
When dragging a grouped object into another Group in the Outliner, SkUp "sometimes" adds that object to all clones of that Group, even when we want the object added to only that one Group. Interesting b/c SkUp acts as if the Group clones are Components, but the clones are Groups and not Components. There doesn't seem to be a pattern b/c sometimes it does not change or add the object to the other Groups.
We've been ignoring this for a few years now and work around by just regrouping for that one instance of the clone. But are groups supposed to act as Components when dragging in an object w/i the Outliner?
I searched to see if anyone else mentioned it on the forum (no joy), so I thought it was time to ask since we must have missed this somewhere...
Thx again for the help.
/D
-
Thats interesting Dave, I've not come across this before, but it sounds like fun to try and track down!
Chris
-
cool - never got the idea of using the outliner for drag - and - drop actiions.
definitely have to try this (if I wanted a group to beincluded in another group I did cut - enter group - paste in place (very quick when using shortcuts)) -
That is interesting. It's not quite component behavior because one large group can be edited without a change to the others.
So, is this a feature or a bug? If it is a feature, how can it be leveraged? Hmmm....
-
.
Funny that we've been fooling w/ this for a long time and I just assumed it was another undocumented trick.You'll notice tho as you use the Outliner for drag/drop nesting of the clones, that the results are unpredictable (and therefore not really a feature"..;-) Some of our object outlines are 5 or 6 nests deep, but the same behavour occurs even with a simple cluster.
Hope that helps, pls let me know when you know...thx again.
/Dennis
.
Advertisement