Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft: Saving values in input fields and copy-checkbox when the "continue" checkbox is active #13334

Closed
2 tasks done
kaiwas opened this issue Apr 6, 2024 · 5 comments
Closed
2 tasks done
Labels
Feature FR for improvements or new features Missing: 'About' info Missing full 'About' info Missing: tested on dev version UI/UX WB Draft Related to the Draft Workbench

Comments

@kaiwas
Copy link

kaiwas commented Apr 6, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Problem description

If you need to perform an action with the "continue" parameter, a value equal to zero is useful only at the very first activation of the action (because the program cannot know the required value). But after the value has been entered, it would be more correct to save this value if the “continue” checkbox is active.
The example is quite simple. If you need to arrange (or rotate) an object by a certain step, you have to constantly re-enter the data (for example, step 1000 mm). It's very tiring.
If at some stage the step is 1000 mm. you will need to change it to another, it is not difficult to do. But the value =0 is essentially completely useless. Because copying an element in place of the original object is very rarely required. If necessary, you can simply change the value to zero.

Also, the “copy” checkbox is reset if it is activated for the “move” tool and is saved only for the “copy” tool. It is not right. If the user has activated this toggle, it should remain enabled. (exactly the opposite. If the checkbox for the “copy” tool is turned off, it should not be turned on again). This will speed up the process and won't require you to exit the tool and start another one.

Short summary. For repetitive operations, you have to do too many unnecessary steps.
For comparison, similar operations in Corel Draw. (for comparison in the speed of performing identical actions).

video-2024-04-06_16.08.53.mp4

One more example. At any stage, you can change the values and get a predictable result without constantly entering values. You can quickly create hundreds of copies of an object at the desired increments.

video-2024-04-06_16.45.17.mp4

Full version info

Any Versions

Subproject(s) affected?

Draft

Anything else?

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@kaiwas kaiwas changed the title Saving values in input fields when the "continue" checkbox is active Saving values in input fields and copy-checkbox when the "continue" checkbox is active Apr 6, 2024
@kaiwas kaiwas changed the title Saving values in input fields and copy-checkbox when the "continue" checkbox is active Draft: Saving values in input fields and copy-checkbox when the "continue" checkbox is active Apr 6, 2024
@maxwxyz maxwxyz added WB Draft Related to the Draft Workbench UI/UX Feature FR for improvements or new features labels Apr 6, 2024
@maxwxyz
Copy link
Collaborator

maxwxyz commented Apr 6, 2024

So maybe there could be a checkbox in the applicable Draft tools to keep the value.

@kaiwas
Copy link
Author

kaiwas commented Apr 6, 2024

So maybe there could be a checkbox in the applicable Draft tools to keep the value.

Yes. This could be arranged as an option. It would be especially nice if this setting was the default.
To be honest, I can’t imagine in what situation the current option might be convenient. but perhaps in some special cases it is really useful.
Zero values and "resetting" parameters are very specific.

@kaiwas
Copy link
Author

kaiwas commented Apr 6, 2024

But if we think logically, the “continue” checkbox itself implies that the user expects the action to be repeated. Any zeroing or resetting of parameters is harmful. Because in this case there is not a continuation, but a new activation of an empty action.
To understand how illogical the current situation is, it is enough to multiply the object with an offset at least 10 times (not just once).

The only time the current situation with input fields can be useful is when we perform manipulations exclusively with the mouse. In this case, the input fields simply show values but are not controls.

@Roy-043
Copy link
Contributor

Roy-043 commented Apr 6, 2024

This a duplicate of #12500.

@Roy-043 Roy-043 closed this as not planned Won't fix, can't repro, duplicate, stale Apr 6, 2024
@kaiwas
Copy link
Author

kaiwas commented Apr 7, 2024

This a duplicate of #12500.

Despite the fact that there are similarities between the topics, these are TWO DIFFERENT PROBLEMS. They solve different problems (although there are overlaps).
In the case of "repeat last action CTRL+R" anything can be used (change color, delete or something). It does not have to involve transforming the object. In this case, when performing repeated steps, there is no way to change those steps because the action is always the same.
In the case of working with fields (closed topic), we simply quickly perform a certain operation when working with fields and have the opportunity to change the parameters if necessary. For example, a pitch of 1000 mm. change to 2000 mm.. after the 5th copy.

If necessary, I can record an explanatory video that will demonstrate the difference between the two topics.

2024-04-07.09-23-52.mp4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature FR for improvements or new features Missing: 'About' info Missing full 'About' info Missing: tested on dev version UI/UX WB Draft Related to the Draft Workbench
Projects
None yet
Development

No branches or pull requests

3 participants