Add an option: Undo/Redo Does Not Select/Unselect

Is this option added to the preferences in Dorico 6?
For some users, this could be the turning point in deciding whether to buy or skip the upgrade to D6. IMHO, of course.

No, there’s no change in this area in Dorico 6.

Okay, my money will stay with me :slight_smile:

@dspreadbury, You know, Dorico is the best, and I couldn’t resist the urge to buy the upgrade to get all the new features. I did so last December. Thank you!

BTW why isn’t it working or what does this option in Preferences mean?
image

Me too. It saves my bacon all the time. You think you’re about to get one note, but you miss a little bit and get the whole measure, (or you want to click a stem for a chord but miss and get the measure) and a quick undo gets your selection back where it was.

5 Likes

Then it would be better to have two undo functions - a simple undo (Ctrl+Z) and a not-so-simple undo (Ctrl+Shift+Z). Which is which - could be an option in the settings (Swap Undo Functions).

For me, the only situations where the undo/redo function should include selection changes are if I select a lot of notes and accidentally click somewhere else and lose the selection. But that’s rare.

This is not exactly what you’re looking for but there is a menu choice that gives you a chronological list of edits from which you can undo up to a selected point. Search “undo history” in Dorico help for more info. “You can open the History dialog in any mode by choosing Edit > and thenHistory.” Maybe you can add it to a key command…. :wink:

1 Like

Right! Chronological. Window is just to see visually what you did and can point to the list where you want to go back. It includes all selection changes. So if you add one note, play whole piece, just select notes and other elements and do that some 50 times, and when you decide to undo last added note, you should press undo 51 time. I understand that many users cannot imagine their lives otherwise, but for me it’s strange.

Go deeper: you add one note, play piece, select elements to see their properties (we don’t have hover-tooltip as it could be very logical) for some 10-20 times, then add another note, again select items for 10-20 times, then you would like to go back to the state before both notes and forward to the state after adding them. The result: instead of pressing undo twice and redo twice you will press 40 times undo and if you want to go back to latest state, press 40 times redo.

Simple feature request - add an option to make Dorico even more flexible for all users.

Such option can be in Preferences and in History window, also in Jump Bar, so users can switch it on the go.

@dspreadbury, did you notice my silent “feature-request” in this post about “hover-tooltips”? I won’t post new feature request because one option cannot be added for 4 years, but just tell me - was there a plan to make yellow info hover-tooltip for notes and other elements? That way we could avoid multiple selections made just to see properties. If we move mouse to status bar on the bottom over “Selection” info line, then the same info is showed in tooltip at the same place (Hmm, why?! Probably some info lines can be longer than the place for it.)

1 Like

No, using Edit—Undo history, you can select the point you want to go back to and it will undo all from that point forward. Or, you could just select the note and delete it. (I understand you were using that as an example and it wouldn’t apply to every situation.)

2 Likes

Exactly the same as pressing Ctrl+Z many times. But I want to undo one-two-three operations but not changing selection to previously selected element. Only if currently selected element doesn’t exist in history, the selection goes off (deselect all), because user didn’t made any action with mouse to select anything else.

If selection should be in the history in line with all editing actions, why isn’t menu browsing put in the history? It’s the same mouse/keyboard action as selecting notes and other objects.

I don’t think it is. Among other things, how would you undo a previous action of opening a menu?

1 Like

Probably we don’t understand each other. My bad English :slight_smile:
I mean browsing through the menu - going from one item to another using cursor keys without clicking on them - it’s the same as we go from note to note using cursor keys.

It can be called - walking from item to item. So walking from note to note is added to History, but walking from menu item to another isn’t added.

Also switching view modes isn’t added to History, but it’s very important for users who need any selection to be able undo. It’s very important to undo view mode because one note added before three selections of other notes in another view mode.

Okay, it’s sarcasm, but seriously, I understand that selection is needed in undo/redo stack for some users, but seems no one here understand that for some it’s very annoying, distracting, disturbing.

And the only thing I can do is to ask for additional option. I guess I’m eligible to do that because we all here are licensed users. Such activity have a name - feature-request (4 years old request). Or at least fix already existing option which doesn’t do what it meant for:

  • Preferences → Note Input and Editing → Follow Selection changes on undo and redo.
    (It’s already here, but doesn’t work or I don’t understand what it is for.)

One single line in code: if option_FollowSelectionChanges is off, then skip selection changes when user do undo/redo. That simple!

@dspreadbury, maybe you can send me a code of Dorico, I will analyze and point a finger to the place, where such row should be added :wink: I will do this for free, of course (for first time) :wink:

I know – my point is that menu browsing doesn’t actually do anything, so there’s nothing to undo. Clicking on items in the score changes the state of those items from unselected to selected. That may not be a change you’re interested in, but it’s a change nonetheless.

Right – and you’ve done this, as have other users over the years. I think the rest of this is just discussion about usability and personal preferences.

1 Like

Of course! Just like someone else wants to have the last word. BTW the purpose of FORUMS is discussions. Where else users can discuss about usability and personal preferences?

Brilliant! You understood me! Right this isn’t needed to put in undo/redo history for many users and as I know I’m not alone in this. Some of our local composers also told me the same, but they don’t discuss here (probably because of some arrogant forum people). They simply suffer silently because they know they can’t influence anything.

Let’s use History window. Okay. Take a look to this image…


If I need to undo 3 edits, then redo them just to listen to changes in music, but in the list it is somewher out of sight, it isn’t normal.

Cubase doesn’t include visibility changes in History because for that it has Undo visibility changes. It doesn’t put selection changes in editing History.

WaveLab - It has Navigation buttons Forward and Backward. It’s in View section and is for navigation. Who wants to go forth and back, uses it. It doesn’t affect editing. It has History like any other normal software in the world, but it don’t put selection changes (navigation) into the History. Exactly this is the best, the golden middle way for all users, in my opinion.

SpectraLayers - It also have history and it stores in it only Range selection and it’s good, in my opinion. But it doesn’t store simple clicking in project, nor playhead position.

VST Live - the same - selection doesn’t go to History.

I use all Steinberg software and I really wonder why Dorico stores every click on notes and other objects in staves.

@asherber, if you don’t like my long blah-blah, you can ignore me and my posts. I won’t be offended. And this will save your time. By the way I like to talk/write. This is the only way I learn English.

1 Like

It just came to my mind that maybe an added Snapshot functionality, like it exists in Lightroom*, would be handy (@dspreadbury)

In a particular moment you click “take Snapshot” and Dorico saves the current situation. You can then freely experiment, make changes, select/unselect, change again, go back and forth…, then take another snapshot. Then a snapshot list exists and you can freely switch between the different snapshots:
See this Lightroom tutorial as an example CLICK.


(*)Dorico design took inspiration from Lightroom. See Hear this, especially starting from 11:13 for the part about Lightroom:

1 Like

+1
I really appreciate the current state of how it’s done. But as you described earlier it can be annoying to undo 10 different selections to only undo one edit. And sometimes I decide to go back to a stage in my project dozens of edits ago…

1 Like

a solution could be to keep the selection changes in undo history only until you make a material change, like adding/deleting a note. As long as you would just keep selecting, deselecting, filtering elements, you would be able to undo/redo those steps. After making an actual edit, the selection changes would be purged from history.

For me and for many users selecting, filtering etc is navigation. Only data is object for undo/redo. WaveLab team knows that. Therefore WaveLab has two stacks - undo/redo for edits and back/forward for navigation. I guess two teams in one company should cooperate.

It’s another dimension of summing problems through the years :frowning:
I’m using Adobe products and never had problems with undo/redo, with navigation. I don’t use Lightroom, but I’m not sure that music software developing team should follow principles that are good in different niche.

2 Likes

?

@ArthurNeeman
Did you hear the podcast (I also indicated the exact time), to understand what “taking inspiration” means in this case?