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

Bug 371319

Summary:	Theme changes are not applied on preference import
Product:	[Eclipse Project] Platform	Reporter:	Michael Pellaton <michael.pellaton>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	emoffatt, gheorghe, pwebster, tom.schindl
Version:	4.2
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:	stalebug
Bug Depends on:	362522
Bug Blocks:

Description Michael Pellaton

2012-02-12 00:56:35 EST

Build Identifier: I20120127-1145

When importing an EPF file containing a different Theme (General > Appearance) the theme change is not applied until Eclipse is restarted. However, other preferences are applied upon every EPF import.

Reproducible: Always

Steps to Reproduce:
1. Start Eclipse in a new workspace
2. Switch the theme to "classic" (Preferences: General > Appearance)
4. Export all preferences to an EPF (File > Export > Preferences)

5. Restart Eclipse in another new workspace
6. Import the previously exported EPF (File > Import > Preferences)
-> the theme change is not applied

7. Restart Eclipse again (in the 2nd workspace from 5.)
-> the theme change is applied

Comment 1 Paul Webster

2012-02-13 08:29:04 EST

Eric, do we have this written down anywhere?

PW

Comment 2 Thomas Schindl

2012-02-13 10:16:16 EST

I guess the css.theme needs to listen for the preference changes and act when the preference is modified

Comment 3 Paul Webster

2012-02-13 10:34:41 EST

I believe there are other limitations here as well, like being unable to change some aspects of already existing SWT widgets, but that's not all it is.

PW

Comment 4 Eric Moffatt

2012-07-25 11:53:53 EDT

In order to fix this properly we'll first have to fix bug 362522 (and its relatives)...if we can't handle a 'live' theme switch then we have no hope of this working correctly.

Comment 5 Eclipse Genie

2019-12-08 12:22:41 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.

--
The automated Eclipse Genie.