Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 342257 - Eclipse should not change OS defaults and apply custom look by default
Summary: Eclipse should not change OS defaults and apply custom look by default
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-08 06:15 EDT by Dani Megert CLA
Modified: 2019-11-14 03:08 EST (History)
6 users (show)

See Also:

Attachments
Picture of out of the box look (28.88 KB, image/png)
2011-04-08 06:33 EDT, Dani Megert CLA 		no flags Details
Picture of mixed world (8.72 KB, image/png)
2011-04-08 06:34 EDT, Dani Megert CLA 		no flags Details
View All 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 Dani Megert CLA 2011-04-08 06:15:52 EDT 
4.1 M6.

Due shipping a custom look/branding instead of following the SWT-way and be native, Eclipse ends up as ugly beast if the user is not using the same theme on his computer. Even worse: as soon as some dialogs are opened the custom look world is left and I have to deal with two different UIs for the same application (see screen shots). Switching to another Eclipse theme improves things a bit.
Comment 1 Dani Megert CLA 2011-04-08 06:21:07 EDT 
Related:
bug 320901
bug 320238
bug 340889
Comment 2 Dani Megert CLA 2011-04-08 06:33:27 EDT 
Created attachment 192809 [details]
Picture of out of the box look
Comment 3 Dani Megert CLA 2011-04-08 06:34:31 EDT 
Created attachment 192810 [details]
Picture of mixed world
Comment 4 Lars Vogel CLA 2019-11-14 03:08: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.

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