[Bf-committers] TFace Breaking, time to rid 'eekadoodle'

[Ton Roosendaal]

Hi,

Ack! I didn't do it after the custom-mesh-layer stuff...
This indeed is destructive.

I'll put on high priority a feature in .blends that:
- allow sub-version numbers for do_versions() (like 2.43.1 etc)
- allow warning prints (menus) to denote a file isn't fully upward  
compatible anymore

Brecht: btw, joining meshes with UVs goes badly wrong atm!

-Ton-

On 21 Nov, 2006, at 12:39, Ton Roosendaal wrote:

> Hi,
>
> I don't understand, current CVS saved files with TFace UVs load fine  
> in 2.42a release for me.
>
> -Ton-
>
>
> On 21 Nov, 2006, at 1:14, Campbell Barton wrote:
>
>> noticed that files in 2.43 wont be able to load UVs, While were at it  
>> could we fix the eekadoodle problem where faces cant have v3 or v4  
>> zero index. and use MAXINT instead, talked abt this khpython and ton  
>> a while ago, the reason not to make this change was that it would  
>> break loading in old blenders.
>>
>> at the moment blender needs to rotate the order of indicies so the  
>> zero index dosnt fall on v3 or v4, using MAXINT would solve this  
>> problem.
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers at projects.blender.org
>> http://projects.blender.org/mailman/listinfo/bf-committers
>>
>>
>>
> ----------------------------------------------------------------------- 
> ---
> Ton Roosendaal  Blender Foundation ton at blender.org  
> http://www.blender.org
>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at projects.blender.org
> http://projects.blender.org/mailman/listinfo/bf-committers
>
>
>
------------------------------------------------------------------------ 
--
Ton Roosendaal  Blender Foundation ton at blender.org  
http://www.blender.org