One bug is annoying me lately.
In my workflow I generally attach a plane to a face via FlatFace because it is just selecting the face and clicking the sketch. Then I change to "translate" mapping via editing the property (either for robustness via expression, or to reposition it in case of a loft). When I do this the support is maintained (it is still the face I used for FlatFace). If I reposition this feature in another order (prior in the tree of the one that originally generated the face), the I get a DAG error.
I think that: when a mapping is changed, the support has to be evaluated to see if it is still compatible with the new mapping. Examples of non compatible supports can be:
1. From FlatFace to translate.
2. From FlatFace to onEdge.
There are basically tons of incompatible combinations.
The detection could be done as here:
https://github.com/abdullahtahiriyo/Fre ... 7cdabf128a
In that commit, it also deletes the support if the new mapping is not valid. I am not sure which should be the solution. I can think of:
1. Delete the support.
2. Annoy the user with a pop-up of TaskAttachment so that he can delete the support, or change it or add more supports to it. (this should be done by the Gui:DocumentObject)
3. Any suggestion?
If you would check that commit and give me some feedback, I would welcome it.ickby wrote: ... summoning ...