[Bf-committers] 2.49: prevent reading 2.5+ ?
blender at erwincoumans.com
blender at erwincoumans.com
Tue Apr 14 02:02:19 CEST 2009
The new mesh data and animation data is new so not "known data" obviously.
So the choice of not keeping a copy of the old mesh data is basically giving
up forward compatibility. That's why I quoted Joe in my previous email.
I hope Joe can briefly explain why it is impossible to keep a
copy/conversion between old and new mesh data.
Thanks,
Erwin
Martin Poirier writes:
>
>
>
>
> --- On Mon, 4/13/09, José Ignacio Romero <jose.cyborg at gmail.com> wrote:
>
>> El lun, 13-04-2009 a las 19:09 -0400,
>> blender at erwincoumans.com escribió:
>> > It hasn't happen before: old Blender versions from
>> 1999 can still read
>> > objects, meshes, camera and ipo/animation curves from
>> todays Blender, and
>> > vise versa.
>> >
>> > Obviously an older Blender version will skip the
>> new/unknown data, the
>> > concern is about known data.
>> >
>> the new mesh data and animato don't qualify as
>> "known data", do they?
>
> That's exactly it.
>
> Martin
>
>
> __________________________________________________________________
> Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now
> http://ca.toolbar.yahoo.com.
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
More information about the Bf-committers
mailing list