[Bf-committers] Socket storage and backwards compatibility

[Dalai Felinto]

Hi,

> What are the ideas about backwards compatibility of the image node/file
output node?

The 'File Output' seems to be pretty backward compatible. The one in trunk
seems like a subset of the one in Tiles.
What is wrong with creating an output node set with the scene parameters
(image type, compression, ...)?

Cheers,
Dalai

2012/5/6 Jeroen Bakker <j.bakker at atmind.nl>

> Hi All,
>
> We have some issues with the new image node. Users are creating files
> with trunk and read them using tiles. And it crashes :)
>
> for example:
>  *
>
> http://projects.blender.org/tracker/index.php?func=detail&aid=31329&group_id=9&atid=524
>  *
>
> http://projects.blender.org/tracker/index.php?func=detail&aid=31300&group_id=9&atid=524
>  *
>
> http://projects.blender.org/tracker/index.php?func=detail&aid=31301&group_id=9&atid=524
>
> These 3 bugs are related to the fact that the new image node, using
> socket storage in stead of the index of the socket. This issue can be
> solved after merging. Just as the new file output node.
>
> Question remains;
> What are the ideas about backwards compatibility of the image node/file
> output node?
>
> Greetings,
> Jeroen & Monique
>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>