Open semhustej opened 2 weeks ago
/cc @Roy-043
Let me comment on this. Saving previously accepted settings is missing in many places (almost everywhere). In the vast majority of cases, all settings are "zeroed out" and have to be re-entered, even if a repeat action is required. This is very sad.
The zero value of the move (after the move action has already been applied) looks especially funny. Nobody ever moves "to zero" and this is useful only for the initial input. And there are many such examples.
https://github.com/user-attachments/assets/0893de0e-8c93-4ef9-95c4-56b9a448d680
@kaiwas I mainly reported the first part of the feature suggestion, which would be similar to how other tools work and lead to consistency of all tools, which is desirable. I am not sure if remembering values is doable and how hard it would be to implement. I did not check other tools. It would be nice for sure.
I mainly reported the first part of the feature suggestion, which would be similar to how other tools work and lead to consistency of all tools, which is desirable.
yes. I understand. It's just that this problem occurs very often. (You will encounter it many more times). Even if the "continue" checkbox is checked. I don't know how difficult it would be to solve this, but the fact remains. We have to re-enter the data over and over again (even if it is repeated, and this is often required). There are almost no options to repeat the last action performed.
Is there an existing issue for this?
Problem description
Priority: low
With most Draft tools, when they are started repeatedly, the last used setting is saved. Draft_Fillet does not save settings when invoking the tool repeatedly. It always defaults to the original settings. This leads to slower workflow, when user wants to use the same settings on the next fillet, which is quite common.
Suggested change:
Settings not saved:
Video describing the behavior:
https://github.com/user-attachments/assets/2e75e5bb-8e63-4924-8aaf-06b271531382
I could reproduce this behavior on 0.22dev and 0.21.2 version.
Full version info
Subproject(s) affected?
Draft
Anything else?
No response
Code of Conduct