[Bf-committers] Re: [Bf-blender-cvs] CVS commit: blender/source/blender/include BDR_editobject.h blender/source/blender/src editobject.c space.c toolbox.c

trip somewhere trip0o at gmail.com
Tue Nov 14 22:12:41 CET 2006


Ok but lets try an example. From frame one to frame 30 two key frames are
set on one object. Later you deside making a duplicate of that object say 30
times and changing it's end postion at frame 30 would be a neat effect.
Duplicating this object and moveing the object to it's postion on frame 30
and entering Insert Loc 30 for all of them one at a time is a slow as you
will need to select them one at a time.
But b you come to find out after you jump back to frame one and hit play
they all end up at teh last objects Insert Loc since they all share the same
ipo.

At this point you know have to either start all over or make all of them
each at a time single user, Plus theres that annoying confirm box
underneath it.

All when simpley at frame 30 I could have selected them all and pressed one
Single user mode button to make them all remain in their location at frame
30.

Do you see my jive? It's a user thought that would happen and it instead has
to conform to a different unthought of system.


On 11/14/06, Martin Poirier <theeth at yahoo.com> wrote:
>
>
> --- trip somewhere <trip0o at gmail.com> wrote:
>
> > Silly question on this multiple select asign
> > feature. Make single user and
> > insert Loc on frame number from duplicate objects.
> > Am I correct that if I select several objects that
> > have the same ipo and I
> > so chose to re adjust the're postion and select all
> > of them and apply Insert
> > Loc for instance they would all get that location
> > ipo.
>
> If they all have the same IPO block beforehand, yes.
>
> > If they have single user or whatnot.
> > When pressing Enable single user mode it only works
> > on the last selected.
>
> Of course, using the single user function "split" the
> selection from the other users of the datablocks, it
> doesn't split off all users of the datablocks.
>
> > A clean flow would be that it creates single user
> > ipos by default when they
> > do not   have the same location rotation size
> > whatever...
>
> The IPOs won't be shared unless you assign them
> manually (in the IPO window). Inserting keys always
> creates new IPO blocks if none are present and inserts
> into the current block if possible.
>
> > Or am I missing something?
>
> I'll leave that one for others.
>
> Martin
>
>
>
> ____________________________________________________________
> ________________________
> Cheap talk?
> Check out Yahoo! Messenger's low PC-to-Phone call rates.
> http://voice.yahoo.com
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at projects.blender.org
> http://projects.blender.org/mailman/listinfo/bf-committers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://projects.blender.org/pipermail/bf-committers/attachments/20061114/f53ec4c9/attachment.htm


More information about the Bf-committers mailing list