Page MenuHome

Fix T65990: UV Layout Export error with 'Modified' checked
ClosedPublic

Authored by Philipp Oeser (lichtwerk) on Jun 21 2019, 1:10 PM.

Diff Detail

Event Timeline

This revision is now accepted and ready to land.Jun 21 2019, 1:17 PM
io_mesh_uv_layout/__init__.py
144

What happens when the operator is called from another operator which also called to_mesh on some objects, but which should remain valid when this operator is done?

Philipp Oeser (lichtwerk) added inline comments.
io_mesh_uv_layout/__init__.py
144

That is a good question, current design for freeing the meshes is done via obj_eval.to_mesh_clear() afaict -- introduced in rB32d5d127cb49. meshes are outside of main, owned by ob, cannot be removed from bpy.data.meshes...
Afraid I have to pass this question on to @Sergey Sharybin (sergey)... [not sure if above usecase is supported still... worst case scenario: create them again in the other addon?]

io_mesh_uv_layout/__init__.py
144

Oh, hold on, should we be using bpy.meshes.new_from_object() instead of object.to_mesh() then?

Philipp Oeser (lichtwerk) marked 2 inline comments as not done.Jun 21 2019, 2:53 PM
io_mesh_uv_layout/__init__.py
144

Like D5114?