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

Bug 241734

Summary:	[PropertiesView] Properties View does not remember preferences between sessions
Product:	[Eclipse Project] Platform	Reporter:	J. Matt Casson <matt.casson>
Component:	IDE	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	minor
Priority:	P3	CC:	Kevin_McGuire
Version:	3.4
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
See Also:	https://bugs.eclipse.org/bugs/show_bug.cgi?id=541438
Whiteboard:	stalebug

Description J. Matt Casson

2008-07-22 15:22:27 EDT

Build ID: I20080617-2000

Steps To Reproduce:
1.Open the properties view in Eclipse.
2.Turn on "Show Advanced Properties", turn off "Show Categories", adjust the width of the Property column to 200.
3.Restart Eclipse.
4."Show Advanced Properties" is off, "Show Categories" is on and the Property column width is back to 335.


More information:
Was saving the view state simply overlooked?

Comment 1 Eric Moffatt

2008-08-18 14:18:37 EDT

Not really...when we did the original version of the PropertySheetPage we didn't even have a mechanism to save state on views.

This is not as trivial a fix as it may appear; this view is an instance of a PageBookView. This is a special type of view container that managed zero or more views, any one of which may have savable state. I'm going to mark this as 4.0 since I think the fix may be too deep to put into the 3.3 stream.

Kevin, this is in an area that Paul and I have been discussing; it's tied in with MultiPageEditors and MultiEditor issues. What we have are 'sub' stacks (the tabs along the bottom of the MPE and the set of actual view instances under a PageBookView like the Console). This is now further complicated by the fact that any of the 'leaf' views (parts) may support locally savable state and, perhaps, a 'dirty' state for which we'd have to provide some affordance. Something to chew on...;-).

Comment 2 Dani Megert

2013-06-05 10:42:40 EDT

Removing outdated target milestone.

Comment 3 Eclipse Genie

2020-11-16 12:06:06 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.