06-28-2013, 12:27 PM
There were only two exporters I played before and the only one I knew it was "freezing" the object was yafray plugin. For the POV-Ray I thought it was forgotten. 
That's probably remains for long time and until now no one has pointed this before. So, it seems the people didn't have problem with that.
If someone is exporting to an other modeller tool, maybe this behaviour would be appropriated, but for a render software it would be better export the frozen object (and in this case, only those exporters would use such command).
Well, I think that now we have a possible problem thinking about change this behaviour.
___
At some moment when I was studying Erlang, I read or someone told me that this king of construction should be avoid: Shs = St#st.shapes.
So, the best code for your suggestion would be:
That's probably remains for long time and until now no one has pointed this before. So, it seems the people didn't have problem with that.
If someone is exporting to an other modeller tool, maybe this behaviour would be appropriated, but for a render software it would be better export the frozen object (and in this case, only those exporters would use such command).
Well, I think that now we have a possible problem thinking about change this behaviour.
___
At some moment when I was studying Erlang, I read or someone told me that this king of construction should be avoid: Shs = St#st.shapes.
So, the best code for your suggestion would be:
Code:
export(Exporter, Name, Ps, St0) ->
#st{shapes=Shs} = St = wings_view:freeze_mirror(St0),
...