Skip to content
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

Allow the setting of a custom ToolManager and MapTracker #311

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

MSementsov-Ibk
Copy link
Contributor

Signed-off-by: Michael Sementsov michael.sementsov@hotmail.de

Sigend-off-by: Michael Sementsov <michael.sementsov@ibykus.de>
@MSementsov-Ibk MSementsov-Ibk force-pushed the settable-maptracker-and-toolmanager branch from bf9e307 to a0e44ae Compare October 5, 2018 09:26
@@ -976,9 +988,9 @@ public int getDPI() {
* @param activeMapTracker the tracker that managers
*/
public static void setActiveMapTracker( ActiveMapTracker activeMapTrackerToSet ) {
if (activeMapTracker != null ){
/*if (activeMapTracker != null ){
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the reason behind to comment this block? It there a usecase to allow to re-set map-tracker?

*
* @param toolManager the new tool manager
*/
public static void setToolManager(IToolManager toolManager) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where is this Method called from and what is the reason to (re)set toolManager Singleton?

@MSementsov-Ibk
Copy link
Contributor Author

@fgdrf We use both of these methods inside our own products, where we have a custom ToolManager and ActiveMapTracker. There's no direct benefit for uDig, but having the option to set these would be nice. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants