You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
InfoFrame tool creates a single InfoFrame. If a new selection is done while InfoFrame is opened, its content is replaced by the new selection. That way, there is always one single info frame opened.
When using the keyboard shortcut, a new InfoFrame is created, whether it already exists or not. The user may end up with dozains of opened info frame. In this case, when a new selection is done, it is quite difficult to know which info frame is changed.
I think normal InfoFrame behaviour should be the first one (single frame), but there is room and need for the second behaviour which could be called "list". It could be something like an infoframe with a name and should not be updated when the selection is changed. On the other hand, it should be possible to perfom set operations like unioning or intersecting between two or more lists.
The text was updated successfully, but these errors were encountered:
we've got the plugin placed in several menus(see below) + the toolbar (as tool).
there is already a UniqueFeatureInfoPlugIn but that window does seem to get replaced when FeatureInfoPlugIn is run. my vote'd be to fixup UniqueFeatureInfoPlugIn to stay open and have FeatureInfoPlugIn use one window instance over the whole application where info selections are updated.
InfoFrame tool creates a single InfoFrame. If a new selection is done while InfoFrame is opened, its content is replaced by the new selection. That way, there is always one single info frame opened.
When using the keyboard shortcut, a new InfoFrame is created, whether it already exists or not. The user may end up with dozains of opened info frame. In this case, when a new selection is done, it is quite difficult to know which info frame is changed.
I think normal InfoFrame behaviour should be the first one (single frame), but there is room and need for the second behaviour which could be called "list". It could be something like an infoframe with a name and should not be updated when the selection is changed. On the other hand, it should be possible to perfom set operations like unioning or intersecting between two or more lists.
The text was updated successfully, but these errors were encountered: