Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 337102

Summary:	[Workbench] Reusing a view name causes issues with ViewParameterValues
Product:	[Eclipse Project] Platform	Reporter:	Tim Moore <tmm-bugs.eclipse>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P5	CC:	prakash
Version:	3.7	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	stalebug

Description Tim Moore

2011-02-14 06:35:35 EST

Build Identifier: M20100909-0800

In our RCP app we've created a view called "Types", the same name as org.eclipse.jdt.ui.TypesView. We'd prefer not to add the latter to our configuration as we don't use it, but we need the plugin for other reasons.

In any case I noticed that the Show View (View: ...) keyboard shortcut for our Types view was missing the "Types" text - all the others work fine. This is because in ViewParameterValues a map from name -> id is being generated, clearly only one id can win for each name. Possibly, there are similar problems in other IParameterValues?

I'm not sure what to suggest. I'd have thought that the map would make more sense in the other direction, it certainly seems to be used that way more often (as here) - but it's API now (?) so that might be difficult. I guess this is a rare case but it's nontrivial to track down the cause when you do see it.

Reproducible: Always

Comment 1 Ankur Sharma

2011-02-14 06:56:47 EST

Redirecting to Platform/UI

Comment 2 Paul Webster

2011-05-25 08:18:27 EDT

You're right, Tim, the problem is that it is API.  A lot of the command schema was created to provide user-readable feedback, like the labels for IParameterValues.  In this case, not considering that the IDs are unique and the names don't have to be.

I'm not sure how to fix it either, as it is definitely API.

PW

Comment 3 Lars Vogel

2019-11-14 02:22:24 EST

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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.