To quote myself, I do think this feature would be an effective addition, to address various workflows. It’s not an impossible solution.
While we don’t rule this out for the future, it’s not something we anticipate changing any time soon.
It’s a bug not in program, but in attitude.
Many users asked this for years.
@dspreadbury, please take this a bit more serious. If any other operation is filtered out from including into Undo/Redo stack, then also selection of notes can be excluded from adding in the stack after program checked the state of checkbox in Preferences.
This is the logic and default approach in every software in the World - if something isn’t needed by one half of users while it’s needed by other half, option in Preferences is the only solution. But you want to regulate how we work. It’s very bad for future love on Dorico.
@wing, it’s not solved. Maybe next decade ![]()
Add an option: Undo/Redo Does Not Select/Unselect - Dorico - Steinberg Forums
Hi @ArthurNeeman, can you imagine what would happen if each user would state something like that, when one’s desired functionality is not being (jet) implemented?
I would humbly suggest to be happy about what we already have, and just trust the Team for future development.
And, in a certain way, yes: the Team is the creator of the software and it can freely, “undemocratically” decide what will be implemented (considering the small number of Team members, the many functionalities to be still implemented and the fact that everyone has its own desires). Even if I know how the hope that one’s desire will be accomplished "tomorrow " can be frustrating.
I stop reading your comment right after this statement. One’s??? Read the forum and count user replicas and likes. Then multiply this number with 100, because very many users are silent just because they don’t want to struggle. And that really doesn’t mean the developers are right in their position.
The problem with trying to judge the “popularity of ideas” on a forum is that the people who disagree with an idea (or have other priorities) will often not express it, and so are not heard.
This doesn’t mean functionality desired by just one single person – it refers to someone’s preference, regardless of how many people share that preference.
Sorry @ArthurNeeman, English is not my native language. To better express my thought I would now substitute “one’s” with “the”:
@Christian_R your use of the correct English is admirable.
I can say as a native English speaker you used it correctly! “One’s” simply means an unspecified person, so it makes sense with what you said before referring to each user.
While I am on the side of the fence that wants this as an added preference, I don’t think being combative toward the team is very helpful or productive. They’re juggling millions of requests and every user has different priorities.
I’ve been using Cubase a bit more lately, and there’s an toggle button preference you can add to the top menu bar which is really helpful, for toggling “automation follows events.” There’s also other various toggle buttons you can add for switching between editing workflows. Sometimes you want to work one way, and sometimes the other way, depending on the task.
It’s had me thinking such a button would be nice to have on the Dorico menu somewhere – so when you know you’re about to do a difficult selection, you could toggle on “add selection to undo/redo stack.” Just an idea. Though I started this thread, three years later I’ve learned to live with the way it is. I would love to see it change, but there’s even bigger priorities in my opinion - all in due time!
It annoys me about half the time, and the other half it’s really useful. The problem is I don’t know which side the coin will land on until I need it to work that way or I don’t. A preference switch wouldn’t help me in the slightest, as roughly 50% of the time it would be in the wrong state.
Just my 2¢…
Of course it’s not that prioritative than other thousand requests made by users who uses finished software in its 6th generation.
For 9 years it is simplier not to use Undo/Redo, but move selected elements back to their positions that they was before uncountable selections
ARE YOU SERIOUS???
P.S. “One” like “someone” also means not more than one. Our nationality, language and expression doesn’t change the fact, that there should be an option "include selection in undo/redo history" in Preferences just because undoing selection isn’t standard for any other software we use for many decades. I don’t know any other software with such strange behavior.
And that option should have been since very first version, just because it is NOT A STANDARD! What could be misunderstood here?
@dspreadbury, if there could be a possibility to read next Undo record (its title) with the Lua script, then it would be game changer - we can make a script that reads next History record, check its name if it contains “select”, skip it and read next until meet something really undoable/redoable except selection.
Why we click (select) other elements at all? Simple - to have info about them on bottom bar. If there will be yellow info “balloons” on mouse-over, maybe we could click less and undo/redo history can live as is. Others could write their reason why they select elements at all.
Context clues, friend. In that context, “one” and “one’s” have exactly one meaning in colloquial English.
Another try.
If you select, for example, 20 notes and then another 4 notes and need to undo previous operation on previously selected one note, you should press Undo 4 times (deselect, deselect, select, undo). Just to undo one operation! For me it’s nonsense and very annoying.
@clancyweeks, I’m trying my best in non-native language. I bought Dorico years back just because Cubase had the worst score editor. Now Cubase have the same Dorico (a bit simplier), but I still upgrade Dorico because I use everything made by Steinberg.
Sorry. Forgot you were a non-native English user. My bad.
But, when it is pointed out that one has misunderstood something written in a language that is not one’s own, it is sensible to accept the correction.