Bug 114623 - [MPE] [PropertiesView] Multi-page views can clear Property View entries
Summary: [MPE] [PropertiesView] Multi-page views can clear Property View entries
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-01 15:14 EST by Eric Moffatt CLA
Modified: 2019-09-06 15:29 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Moffatt CLA 2005-11-01 15:14:20 EST
The handling of the selection here is inconsistent at best...try this:

Import / check out / create a plugin project with some extensions in it.

Open the Property View

Open the 'MANIFEST.MF' file (notice that we've lost the entry that was 
displayed when we clicked on the file in the PE)

Now, alternate between re-selecting a file in the PE (to show its properties) 
and selecting other tabs in the editor. It's somewhat indeterminate but it 
appears that if you select a 'text' oriented tab (i.e. 'build.properties'), re-
select a file in the PE and then select a tab that has already been displayed 
then the property view maintains showing the file. If its the first time that 
the editor tab has been displaye then the property sheet goes blank. (lazy 
creation issue??)

Also, until you select a text-oriented tab you'll lose the file every time you 
change tabs, even when switching between two 'populated' tabs...
Comment 1 Paul Webster CLA 2006-09-28 15:17:09 EDT
Is this still a problem in 3.3?

PW
Comment 2 Denis Roy CLA 2007-06-22 09:33:08 EDT
Changes requested on bug 193523
Comment 3 Eclipse Webmaster CLA 2019-09-06 15:29:46 EDT
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.