You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Object rotation with respect to the viewport does not work as expected. This is because Blendit does not track changes made to the viewport. And when regenerating .blend file the viewport is fixed
When rotating an object along the viewport axis:
orient_type and orient_matrix_type, in bpy.ops.transform.rotate, is set to 'VIEW'
When rotating an object along a particular axis (X, Y, Z):
orient_type and orient_matrix_type, in bpy.ops.transform.rotate, is set to 'GLOBAL'
In an ideal world I'd like Blender log bpy.ops.transform.rotate in the 'GLOBAL' context.
Without that I'd like to subscribe to bpy.ops.transform.rotate events, using the Blender Message Bus, and then store the bpy.types.RegionView3D values. (I'm not sure how to.)
This would, however, be an imperfect solution as the viewport can change between the time the event is published and bpy.types.RegionView3D values are read.
The text was updated successfully, but these errors were encountered:
Object rotation with respect to the viewport does not work as expected. This is because Blendit does not track changes made to the viewport. And when regenerating
.blend
file the viewport is fixedWhen rotating an object along the viewport axis:
orient_type
andorient_matrix_type
, inbpy.ops.transform.rotate
, is set to'VIEW'
When rotating an object along a particular axis (X, Y, Z):
orient_type
andorient_matrix_type
, inbpy.ops.transform.rotate
, is set to'GLOBAL'
In an ideal world I'd like Blender log
bpy.ops.transform.rotate
in the'GLOBAL'
context.Without that I'd like to subscribe to
bpy.ops.transform.rotate
events, using the Blender Message Bus, and then store thebpy.types.RegionView3D
values. (I'm not sure how to.)This would, however, be an imperfect solution as the viewport can change between the time the event is published and
bpy.types.RegionView3D
values are read.The text was updated successfully, but these errors were encountered: