vkbo
Project Content: One Click Navigation
Proposed Feature
Add preference in setting to toggle on/off one click navigation in Project Content.
One Click Navigation
By one click navigation I mean that I just need to click once to open given project content element, and not have to make double click.
Why I propose this feature
For 2 reasons:
- It makes confused when in Project Content I have selected other note/chapter that edit/check.
- I often jump between scene I write and once I currently writing.
Yes, it could be made as an optional feature, but keep in mind that the undo history is cleared whenever another document is loaded. The undo history is associated with the document itself, and handled by the Qt library in private objects, so there isn't much I can do in the app to preserve it.
Would you also want this to apply to arrow key navigation, or only on mouse click?
That said, I'm considering adding a caching feature that keeps the last few documents in memory, which would allow both quicker switches between them as there is no loading from file, and also preserve the undo history. This is covered in feature #1440. Your request may be more useful after this one is implemented.
Thanks @vkbo for quick answer.
Yes, it could be made as an optional feature, but keep in mind that the undo history is cleared whenever another document is loaded. The undo history is associated with the document itself, and handled by the Qt library in private objects, so there isn't much I can do in the app to preserve it.
I didn't know that, I myself program, but in Godot/GDScript and Python/Gtk (I just started with Gtk).
That said, I'm considering adding a caching feature that keeps the last few documents in memory, which would allow both quicker switches between them as there is no loading from file, and also preserve the undo history. This is covered in feature #1440. Your request may be more useful after this one is implemented.
No problem, I'm patient.
Would you also want this to apply to arrow key navigation, or only on mouse click?
I didn't realize that I can navigate using arrow key navigation in this app. So for me it could be only mouse click, but if we consider other users, than arrow navigation also should have this feature, but as separated preference.
I would not want to add this for arrow up/down as the overhead of loading a document each time would make it hard to scroll through the items using arrows. It could be implemented with a delayed trigger though. A 500 ms delay is usually enough to avoid triggering a backlog of queued GUI tasks.
I don't have to wait for #1440 to add this, but #1440 would help on the clearing undo cache issue.
I actually wouldn't expect the document to change on arrow navigation. If I was keyboard only, I would expect it to act as it does now. Updating on each arrow key would be equivalent to changing each document on mouse hover. eew. ;)
Personally, I'm navigating all over the place as it is, so I'm already losing the undo history and have never missed it.
This is a whole new layer of complexity, but you could get around the loss of undo history by maintaining a revision history of {n} backup files, each saved if any changes have been made. Then you would need UI for inspecting document history, showing diffs, etc. etc.
Apologies, I'm about to ramble a bit...
FWIW, my workflow in Scrivener was to have two open documents, the one I was writing in "pinned" and if I made a change that affected other parts of the manuscript, I'd pull them up in the second document, integrate the changes (or at least make notes), then return to where I was writing. In NW I pull up the second document in view mode and if edits are needed open it for editing, make changes, then go back. That's possibly the only functionality I miss. This also makes me long for forward/backward navigation in the document window; sometimes I lose track of where I was working in the first place!
This is a whole new layer of complexity, but you could get around the loss of undo history by maintaining a revision history of {n} backup files, each saved if any changes have been made. Then you would need UI for inspecting document history, showing diffs, etc. etc.
Yes, I've considered implementing versioning. There are a few closed tasks on it. At the end of the day, the backup solution provides a de facto per-session version copy. You can also duplicate documents internally in the app to keep earlier drafts if you wish.
I have considered adding a way to reset a given document to the version it was at the start of the session. Precisely by storing a copy of it temporarily. But dealing with diffs is a messy business, and if it does get added, it will be quite a long way down the list. There are too many more pressing features to add.
FWIW, my workflow in Scrivener was to have two open documents, the one I was writing in "pinned" and if I made a change that affected other parts of the manuscript, I'd pull them up in the second document, integrate the changes (or at least make notes), then return to where I was writing. In NW I pull up the second document in view mode and if edits are needed open it for editing, make changes, then go back. That's possibly the only functionality I miss. This also makes me long for forward/backward navigation in the document window; sometimes I lose track of where I was working in the first place!
Backward/forward navigation in #1292 has been replaced with the #1440 idea, and would solve several of these use cases. I may add the navigation part, but it would hook into the #1440 framework.
Hello,
Sorry, i've read 1292 and 1440 discussions, but I don't understand how to get the behavior for one-click ?
Thanks
Both #1292 and #1440 are still open tickets, which means they have not been added yet.