#19275 closed enhancement (fixed)
[Patch] Relation list panel: Direct option for history viewer
Reported by: | skyper | Owned by: | GerdP |
---|---|---|---|
Priority: | normal | Milestone: | 20.05 |
Component: | Core | Version: | |
Keywords: | template_report relation list history | Cc: |
Description (last modified by )
What steps will reproduce the problem?
- In Relation list panel select a relation
Ctrl+H
or context menu
What is the expected result?
The history viewer of the relation opens respectively an item "History"
What happens instead?
The general dialog to download an object's history opens respectively no item
Please provide any additional information below. Attach a screenshot if possible.
Please, provide an option to open the history of relations from the relation list directly. Thanks
I noticed that the "History" item is also not present in selection list's context menu.
Relative:URL: ^/trunk Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last:Changed Date: 2020-05-21 00:29:30 +0200 (Thu, 21 May 2020) Revision:16472 Build-Date:2020-05-21 01:30:46 URL:https://josm.openstreetmap.de/svn/trunk
Attachments (5)
Change History (35)
comment:1 by , 4 years ago
Summary: | Relation list: Support history viewer → Relation list: Direct option for history viewer |
---|
by , 4 years ago
Attachment: | 19275.patch added |
---|
comment:2 by , 4 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
Summary: | Relation list: Direct option for history viewer → [Patch] Relation list: Direct option for history viewer |
comment:3 by , 4 years ago
I reused part of the code changes from the solution for #18918 in class ChangesetContentPanel
comment:6 by , 4 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Summary: | [Patch] Relation list: Direct option for history viewer → [Patch] Relation list panel: Direct option for history viewer |
follow-up: 13 comment:7 by , 4 years ago
Your changes are nice but I was not talking about the relation editor but about the relation list panel.
comment:8 by , 4 years ago
Description: | modified (diff) |
---|
comment:9 by , 4 years ago
Something is broken now:
- Download an area
- Select a relation
- Press
Ctrl+H
(history dialog opens, fine) - Edit the selected relation
- Close the relation editor
- Press
Ctrl+H
again (warning appears: "Please select at least one already uploaded node, way, or relation.")
Plus, the following shortcut conflict appears.
2020-05-24 21:00:59.044 INFO: Keystroke ctrl pressed H is already assigned to org.openstreetmap.josm.actions.HistoryInfoAction@470978ba, will be overridden by org.openstreetmap.josm.gui.dialogs.relation.MemberTable$1@209827f8 2020-05-24 21:00:59.045 INFO: Registered toolbar action action/historyinfo overwritten: org.openstreetmap.josm.actions.HistoryInfoAction gets org.openstreetmap.josm.gui.dialogs.relation.MemberTable$1
comment:11 by , 4 years ago
Yes, it does as it avoids to create a 2nd HistoryInfoAction in Membertable.
comment:12 by , 4 years ago
Above regression is fixed with r16495.
I'll look at the relation list tomorrow.
by , 4 years ago
Attachment: | history-popup1.PNG added |
---|
by , 4 years ago
Attachment: | 19275.2.patch added |
---|
follow-up: 14 comment:13 by , 4 years ago
Replying to skyper:
Your changes are nice but I was not talking about the relation editor but about the relation list panel.
Sorry for the misunderstanding.
We have a standard popup for relations which contains the actions like Edit, Duplicate, ..., Download incomplete members of selected relations. I can add History to this menu so that it is always displayed when this standard menu is used or I can add it only in the Relation list.
The patch implements the latter.
follow-up: 19 comment:14 by , 4 years ago
Replying to GerdP:
Replying to skyper:
Your changes are nice but I was not talking about the relation editor but about the relation list panel.
Sorry for the misunderstanding.
That can happen, no problem.
We have a standard popup for relations which contains the actions like Edit, Duplicate, ..., Download incomplete members of selected relations. I can add History to this menu so that it is always displayed when this standard menu is used or I can add it only in the Relation list.
The patch implements the latter.
As in selection list panel, history is only available as button but missing in the context menu, I would go for the general solution. The command stack panel can profit from it, too. But wait a minute, for the other panels history is not bounded to relations, so I am not sure how to handle this.
Is there a general context menu for objects or only one per object type?
I do not find "duplicate" in Tags/Memberships panel. Does it have an own menu?
Command stack panel has only a minimal context menu, e.g. separate ticket?
follow-up: 16 comment:15 by , 4 years ago
In fact I'd prefer to enable the Ctrl+H shortcut but so far I failed. It probably makes no sense to add all possible actions to each context menu. I am not a GUI designer, so I don't know what's preferred in general.
comment:16 by , 4 years ago
Replying to GerdP:
In fact I'd prefer to enable the Ctrl+H shortcut but so far I failed. It probably makes no sense to add all possible actions to each context menu. I am not a GUI designer, so I don't know what's preferred in general.
How does it work in selection list?
comment:17 by , 4 years ago
Found a solution. Difference is that the relation list uses a JList, not a JTable.
by , 4 years ago
Attachment: | 19275.2b.patch added |
---|
alternative solution which adds History to the standard context menu for relations
by , 4 years ago
Attachment: | 19275.2c.patch added |
---|
3rd alternative which enables Ctrl+H for the relation list
comment:18 by , 4 years ago
The solutions for the context menu need a bit more work to disable the button when only new relations are selected,
the 3rd solution handles this case already.
comment:19 by , 4 years ago
Replying to skyper:
Is there a general context menu for objects or only one per object type?
There is only one for relations. That one is also used in the Relation Editor.
I do not find "duplicate" in Tags/Memberships panel. Does it have an own menu?
yes, and it doesn't use the relation menu.
Command stack panel has only a minimal context menu, e.g. separate ticket?
No idea. I would not search for History there. A command cannot be changed or duplicated or what else is possible with OSM objects.
follow-up: 21 comment:20 by , 4 years ago
So, for the relation list panel it is fine to use the same menu than the relation editor.
Other panels have their own context menu.
You can select the object in command stack why not look at the history directly ?
follow-up: 22 comment:21 by , 4 years ago
Replying to skyper:
So, for the relation list panel it is fine to use the same menu than the relation editor.
Other panels have their own context menu.
The selection list panel also shows the relation menu, for nodes and ways all the relation specific actions are disabled.
You can select the object in command stack why not look at the history directly ?
Many commands contain multiple objects, some only new objects. A History action in the context menu would suggest that the history is somehow related to the command.
comment:22 by , 4 years ago
Replying to GerdP:
Replying to skyper:
So, for the relation list panel it is fine to use the same menu than the relation editor.
Other panels have their own context menu.
The selection list panel also shows the relation menu, for nodes and ways all the relation specific actions are disabled.
Well, history is missing for all objects in selection list panel.
comment:23 by , 4 years ago
There is the history side button. If we add the action to the context menu we should remove that, right? Would mean a change in the GUI without any additional functionality. Why would we do that unless we remove all side buttons and add them to the context menus?
follow-up: 25 comment:24 by , 4 years ago
So far most of the side buttons have a duplicate entry in the context menu. I meant, simply an additional entry without removing the side button but, may be, we have to rethink context menu <-> side button.
follow-up: 27 comment:25 by , 4 years ago
Replying to skyper:
So far most of the side buttons we have a duplicate entry in the context menu.
Funny, I came to the opposite result after a short check. So let's say there is no obvious system right now.
I meant, simply an additional entry without removing the side button but, may be, we have to rethink context menu <-> side button.
I think the side buttos have at least one disadvantage. They are always visible and thus the enabled/disabled status has to be refreshed often. The History button should not be enabled when a new way is drawn but it is. Probably a side effect of #10830.
They also require a lot of space, so experts probably disable them after a while.
For a newbe they are probably useful when they show the most often used actions.
Anyway. I think we both use History
often, but a lot of users don't. I fear we overestimate the importance of this action. That's why I would prefer 3rd solution which doesn't add new buttons.
comment:26 by , 4 years ago
Owner: | changed from | to
---|---|
Status: | reopened → needinfo |
comment:27 by , 4 years ago
Owner: | changed from | to
---|---|
Status: | needinfo → new |
I thought about this again and think it is good to have all side buttons in the context menu as you can disable the side buttons of panels completely.
I never asked for a new button, but only for context menu items.
Personally, I am happy, if Ctrl+H
works and I do not care about menu or button for History
. I even forgot about the option to view an objects history without downloading it first.
Well, third solution will do the job, until we have decided about duplicates of buttons in context menus.
comment:29 by , 4 years ago
BTW: I've just learned that the above changes help a lot to analyse if an empty relation is obsolete or if it should be restored by reverting a bad CS.
comment:30 by , 4 years ago
Milestone: | → 20.05 |
---|
Enable Ctrl+H and add History to right click popup menu for member list. The tabs "Parent relations" and "Child Relations" would require more work..