Added the under-the-hood code to support customisation of ... #32
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
September 20, 2020 17:34
…heel used to navigate the traces such as for multiple levels of moving and zooming.
|
Finished customisation of navigation including added support for changing settings via GUI settings page. |
|
Sorry it has been a while, but the project has been on a kind of a hiatus. If you still think this is relevant and want to work on it the code would need to be rebased on current master to fix merge conflicts. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
keys/mousewheel used to navigate the traces such as for multiple levels of moving and zooming.
The code has default values for these keys which can be changed to whatever you want the default to be.
The code also supports loading and saving of these values from settings.
Missing is a GUI settings page that would allow the user to easily change these customisations. I do not plan to add this code myself as I am not well versed in Qt coding, so hopefully someone else can do this. I did provide get/set functions so that the GUI implementer doesn't need to do any "navigation" coding. They can just do a basic settings page and use the get/set functions provided.
See the comment near the top of View.hpp for info about all of this.