Wonder if using some sort of "is_touched"-flag could be exploited here?abdullah wrote:
For example: attach a "flag" to each element and then 'just' check them. I don't know, but in my world it sounds cheap with respect to cpu clock cycles?
Wonder if using some sort of "is_touched"-flag could be exploited here?abdullah wrote:
Reality is more complicated than that.Pauvres_honteux wrote: ↑Fri Dec 03, 2021 6:26 amWonder if using some sort of "is_touched"-flag could be exploited here?abdullah wrote:
For example: attach a "flag" to each element and then 'just' check them. I don't know, but in my world it sounds cheap with respect to cpu clock cycles?
a) the change on the sketch does not modify the end shape generated, but intermediate operations changed the end shape (Auto-update on).
Adding: if "is_touched"-flag is set then delete sketch copy.TheMarkster wrote: ↑Wed Dec 01, 2021 2:10 am ... make a copy of the sketch when opening the task dialog, and then when the user cancels restore the sketch from the copy.
I would rate this higher. If a recompute could be avoided, then this would cover b2 as well.abdullah wrote: ↑Sat Dec 04, 2021 5:56 am in c) one can generally undo the operations. There could be a functionality to undo everything in one go (set the properties back to the state they had upon entering the sketch in edit mode). I am not sure how much such a feature would be used. It is likely something in the order of 0,1% of the cases. However, here you will need to solve and recompute.
I do this quite often, and for me it would be sufficient if only this use case was improved with not recomputing. One rather special and thus in general neglectable use case is my work as helper here, where I check many foreign sketches. But I do this with my own models too, inspect references, look up names, ...case b2) you did not do anything at all (open/close).
Ok. Put it in the tracker and I will eventually take a look.chrisb wrote: ↑Sat Dec 04, 2021 10:04 am I do this quite often, and for me it would be sufficient if only this use case was improved with not recomputing. One rather special and thus in general neglectable use case is my work as helper here, where I check many foreign sketches. But I do this with my own models too, inspect references, look up names, ...
Hi leoheck, that particular thing may be covered by this feature request: [Ticket #4728] Local update function/button