The jump command appears to have an algorithm of keeping the last used command, and then a handful of other commands which appear to be random - but they don’t seem to change either. For example
In this session I’ve used four different commands and the last one appears at the top, followed by four others (Split Flow … etc) which I never use. Go To Bar is redundant anyhow since I’d probably use the Go To entry for that anyhow.
Would it be more sensible to keep a history buffer here and only show it when you hit the down arrow? I’m constantly reusing a couple operations, if they were buffered and displayed in the Jump dialog that would be a big productivity boost. Keeping a buffer of the last five commands would fit the existing jump dialog pattern and be enough.
When you show the jump bar, the text field is pre-populated with the last command you executed, and the list is populated with the five commands you have used most frequently in the whole time you’ve been using the jump bar.
Oh - no I get it, I switch between two computers and a iPad (and just decommissioned and replaced one of the computers) - I think no single one of them has built up a sufficient history yet to be useful.
Would be enormously useful if we are have the same History management dialog in Dorico, too.
It creates log of all operations done during the session and we can easily Undo, or Redo to the desired one.
About the Jump Bar, would be great if we can set the number of stored operations in the Preferences.
A history log is a pretty common feature. The Dorico approach of most common over time is a variation you don’t see often. Seems a bit redundant given the shortcut feature - since we can assign shortcuts mnemonics to most our all time frequently used commands I’d probably find a straight recent history list more useful in the context menu.
