-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Choose which tool to autoselect #122
Merged
Merged
Changes from 7 commits
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
2f91945
Fixes conflict with PropertiesManager renaming
gtache 693213f
Merge branch 'master' of github.com:pcorless/icepdf
gtache db0b33f
Merge branch 'master' of github.com:pcorless/icepdf
gtache a4b0f97
Merge branch 'master' of github.com:pcorless/icepdf
gtache f3f99cd
Merge branch 'master' of github.com:pcorless/icepdf
gtache ef55851
Merge branch 'master' of github.com:pcorless/icepdf
gtache daf55d9
GH-121 Allows selecting which tool to select after drawing aan annota…
gtache ac12aaa
Merge branch 'master' of github.com:pcorless/icepdf
gtache 8b28b29
Merge branch 'master' of github.com:pcorless/icepdf
gtache 2bcaafc
Merge branch 'master' of github.com:pcorless/icepdf
gtache 35cc9b2
Merge branch 'master' of github.com:pcorless/icepdf
gtache 40581e1
Merge branch 'master' of github.com:pcorless/icepdf
gtache ff7226a
Merge branch 'master' of github.com:pcorless/icepdf
gtache 5710f1f
Merge branch 'master' of github.com:pcorless/icepdf
gtache 96ae8be
Merge branch 'master' of github.com:pcorless/icepdf
gtache d7dee59
Merge branch 'master' of github.com:pcorless/icepdf
gtache 984725b
Merge branch 'master' of github.com:pcorless/icepdf
gtache 32aaa6b
GH-121 Fixes conflicts
gtache d5d4b4a
GH-121 Rename annotation tool properties
gtache File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ugh, never really had to think about migrating properties before. How did you decide on PROPERTY_ANNOTATION_INK_SELECTION_ENABLED as the property to set off of? What I might suggest as an alternative is changing the properties keys. The next release is going to be major so we can break anything we can get our hands on api wise. Perhaps change the keys ICEpdfDEfault.properties and similarly in ViewerPropertiesManager to something like this:
application.annotation.highlight.selection.enabled -> application.annotation.highlight.selection.type
Thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, if I remember well I just picked one of them at random, assuming that most people would have the same value for every option.
That'd be cleaner to do that indeed, I think it's a good idea. But I'm wondering if it makes sense to have a property for each annotation tool or if one for all of them would be sufficient?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The original implementation was a separate setting for each tool. I guess this could still be done but it's going to get messy in the properties panel. Perhaps separate properties but still unify as one in the properties panel so they could be tweaked at a later date. I'll leave it up to you as you have good understanding of what your users need.