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
When a measurement (#9750) is saved as annotation the location of the displayed position in the 3D view is fixed and won't update if the referenced object / geometry is moved.
The issue also persists if the underlying geometry is modified, e.g. change the side length of the cube or the depth of a pad: the dimension value is updated, but not the position of the dimension (Elements not rendered correctly if source object changes).
The expected behavior would be, that the measurement needs an update/recompute and will be displayed at the new location of the reference points.
Maybe this is an issue, as the annotation label has no attachment support:
This seems to be a missing recompute. For me it updates if i trigger it manually. That being said it seems to work in simple cases e.g. a measurement on a part Box.
The problem seems to be that we only get signals of our subject but not from it's container (e.g. PD Body). @WandererFan maybe you have an idea how we could solve this?
Is there an existing issue for this?
Problem description
When a measurement (#9750) is saved as annotation the location of the displayed position in the 3D view is fixed and won't update if the referenced object / geometry is moved.
The issue also persists if the underlying geometry is modified, e.g. change the side length of the cube or the depth of a pad: the dimension value is updated, but not the position of the dimension (Elements not rendered correctly if source object changes).
The expected behavior would be, that the measurement needs an update/recompute and will be displayed at the new location of the reference points.
Maybe this is an issue, as the annotation label has no attachment support:
Full version info
Subproject(s) affected?
Core
Anything else?
Code of Conduct
The text was updated successfully, but these errors were encountered: