Bug 160222 - [Graphics] Info marker image harder to read than warning and error markers
Summary: [Graphics] Info marker image harder to read than warning and error markers
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-09 11:45 EDT by Koen van Dijken CLA
Modified: 2019-09-06 16:06 EDT (History)
0 users

See Also:


Attachments
info marker image (10.95 KB, image/bmp)
2006-10-09 11:45 EDT, Koen van Dijken CLA
no flags Details
warning marker image (10.93 KB, image/bmp)
2006-10-09 11:47 EDT, Koen van Dijken CLA
no flags Details
error marker image (10.02 KB, image/bmp)
2006-10-09 11:47 EDT, Koen van Dijken CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Koen van Dijken CLA 2006-10-09 11:45:10 EDT
The info marker image as returned by the IWorkbenchAdapter is harder to read than the error and warning images. This is because the error and warning images have a white line around the entire image, the info image only has it on its right side.

See the attached info.bmp, warning.bmp and error.bmp to see the differences in an actual application.

Please change the info marker image to make its layout the same as the error and warning images (white line completely around the image).
Comment 1 Koen van Dijken CLA 2006-10-09 11:45:44 EDT
Created attachment 51646 [details]
info marker image
Comment 2 Koen van Dijken CLA 2006-10-09 11:47:18 EDT
Created attachment 51647 [details]
warning marker image
Comment 3 Koen van Dijken CLA 2006-10-09 11:47:44 EDT
Created attachment 51648 [details]
error marker image
Comment 4 Boris Bokowski CLA 2009-11-17 11:48:38 EST
Susan is now responsible for watching the [Graphics] category.
Comment 5 Eclipse Webmaster CLA 2019-09-06 16:06:41 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.