Bug 314273 - [package explorer] Build path error decorator (!) looks scrambled for binary projects
Summary: [package explorer] Build path error decorator (!) looks scrambled for binary ...
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks: 308608
  Show dependency tree
 
Reported: 2010-05-25 09:57 EDT by Dani Megert CLA
Modified: 2022-05-29 09:48 EDT (History)
2 users (show)

See Also:

Attachments
Picture showing scrambled decorator (1.70 KB, image/png)
2010-05-25 09:57 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 2010-05-25 09:57:12 EDT 
3.6 RC2.

The build path error decorator (!) looks scrambled for binary projects because the binary project decorator is painted over it.
Comment 1 Dani Megert CLA 2010-05-25 09:57:46 EDT 
Created attachment 169831 [details]
Picture showing scrambled decorator
Comment 2 Markus Keller CLA 2010-05-28 07:58:15 EDT 
We should look at this together with bug 308608, maybe the visual designers have a good idea for a less tall overlay.
Comment 3 Eclipse Genie CLA 2020-06-01 20:05:39 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.

--
The automated Eclipse Genie.
Comment 4 Eclipse Genie CLA 2022-05-29 09:48:00 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.

--
The automated Eclipse Genie.