459939 – With the theme set to "Dark", all annotations settings are set to "dark" theme's default settings on start up.

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

Bug 459939 - With the theme set to "Dark", all annotations settings are set to "dark" theme's default settings on start up.

Summary: With the theme set to "Dark", all annotations settings are set to "dark" them...

Status:	CLOSED DUPLICATE of bug 441135

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	UI (show other bugs)
Version:	4.4.1
Hardware:	PC Windows 8

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	Platform-UI-Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2015-02-13 20:34 EST by Russell Weber
Modified:	2015-02-17 14:57 EST (History)
CC List:	1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Russell Weber

2015-02-13 20:34:07 EST

In eclipse LUNA.  The dark theme was added so that user's wouldn't have to worry about a bright windows experience.  However, with the theme set to "Dark", all annotations settings are set to "dark" theme's default settings on start up.  This renders the annotations unchangeable across sessions. The settings can be modified temporarily and be reflected in the IDE but either they are not saved or are overwritten on start up of eclipse.

steps to recreate.
1. Start brand new eclipse
2. Change theme to dark
3. Change annotation of warnings to not be a yellow highlight, but be a yellow squiggly line instead.  Warnings should now show differently according to the changes we made.
4. Save settings.
5. Shut down eclipse.
6. Restart eclipse in the same workspace.
    >>> Warnings are now/still using the default set by the "Dark Theme".

Comment 1 Ricardo Bochnia

2015-02-15 07:05:23 EST

Duplicate of Bug #441135

Comment 2 Russell Weber

2015-02-17 14:57:04 EST


*** This bug has been marked as a duplicate of bug 441135 ***