Community
Participate
Working Groups
RC2 Create a plugin that contains two views, each with the same ID. Launch a runtime workspace and look in the view menu. Both are there, but only one can ever be activated (the one that was added to the registry first, I'd wager. This may also apply to editors.
What do you think would be a useful conflict resolution policy here?
First view gets registered, any other view gets punted with a message in the log explaining why.
What should constitute "first"? The one with the lowest plugin id, or view id? What about when a new view is installed dynamically? I could imagine an algorithm like: - get all view configuration elements - sort by view id then by plugin id - process them in order - if there's a dup, take the first one only And: - if new views come along dynamically, ignore any dups - it would be better to just redo the above algorithm, but that would require handling removals due to dups
I'd say we should either do whatever we do for other plugins (likely keeping whatever one is given to us first when trolling the registry). If we decide to do something like you suggest then we should ensure that all other registries follow the same rules...
Reassigning bugs in component areas that are changing ownership.
Remy is now responsible for watching the [ViewMgmt] category.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
