adrianinsaval wrote: ↑Mon Jan 10, 2022 1:19 pm
Is there another situation that might trigger the "Links go out of the allowed scope" warning besides what you mentioned chris? Or should it just be changed to mention the body situation every time.
It is triggered whenever a Link property points to a different coordinate system object, without being an
"App::PropertyLinkGlobal" property. So that's probably the case of
App::Part,
PartDesign::Body, probably in general objects that have "
App::GeoFeatureGroupExtension" or "
App::OriginGroupExtension".
Changing a "
App::PropertyLink" or a "
App::PropertyLinkChild" to "
App::PropertyLinkGlobal" is possible, but additional code to recompute the relative local placement of the object would be needed.
Edit: also a change in the global placement of the pointed object (obj B) caused by a change of the placement of its container, would not generate a signal catched by the
onChanged method of the first object (obj A)...