uDIG

GEF Palette MapEditor : unable to change tools in other MapEditors

Details

Description

1. Open a MapEditor
2. open an other one,
3. choose tool "Pan" and pan in map
4. go back to the first editor and switch to Zoom Tool
5. try to zoom in by defining a rectangle in map fails, its still the Pan activated

In general the action chosen by the user in the last opened editor is the tool for all editors. Is only possible in the last opened editor to switch to an other tool.

Issue Links

is depended upon by

Wish - General wishlist item UDIG-1809 uDig 1.3.0 Release

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Jody Garnett added a comment -
Small clarification: uDig still has one global ToolManager - so we expect changing tools to change the tools for all maps.
Show
Jody Garnett added a comment - Small clarification: uDig still has one global ToolManager - so we expect changing tools to change the tools for all maps.
Hide
Permalink
Jody Garnett added a comment - - edited
Wow this one is hurting my mind; bug is confirmed (thanks for the detailed report).

1) ToolManager owns an MapEditDomain that we need to update
2) MapEditDomain.setPaletteViewer(PaletteViewer palette) should be called with the current PaletteViewer
3) The PaletteViewer is very much hidden by the super class of MapEditorWithPalette (as it wants to dynamically switch between a PaletteViewer in a Page and PaletteViewer in the PaletteView)

Going to try and make a "hook" for MapEditDomain; so that MapEditorWithPalette can do the correcting up; as it has access to all its internal details provided by the superclass.
----
Update: That did not work - CustomPalettePage always has "null" for PaletteViewer. I need another idea.
Show
Jody Garnett added a comment - - edited Wow this one is hurting my mind; bug is confirmed (thanks for the detailed report). 1) ToolManager owns an MapEditDomain that we need to update 2) MapEditDomain.setPaletteViewer(PaletteViewer palette) should be called with the current PaletteViewer 3) The PaletteViewer is very much hidden by the super class of MapEditorWithPalette (as it wants to dynamically switch between a PaletteViewer in a Page and PaletteViewer in the PaletteView) Going to try and make a "hook" for MapEditDomain; so that MapEditorWithPalette can do the correcting up; as it has access to all its internal details provided by the superclass. ---- Update: That did not work - CustomPalettePage always has "null" for PaletteViewer. I need another idea.
Hide
Permalink
Jody Garnett added a comment -
I had to move MapEditDomain back to the editor; I have confirmed it works. The slide out palette looks silly when two maps are open side by side; switching to the PaletteView is preferable in this case.

The Palette is updated to the current tool when the editor changes focus.
Show
Jody Garnett added a comment - I had to move MapEditDomain back to the editor; I have confirmed it works. The slide out palette looks silly when two maps are open side by side; switching to the PaletteView is preferable in this case. The Palette is updated to the current tool when the editor changes focus.

People

  • Assignee:
    Jody Garnett
    Reporter:
    Frank Gasdorf
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: