Summary: | Table doesn't respect transparency in column images when using a different row background color | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Chris Gross <schtoo> | ||||||
Component: | SWT | Assignee: | Silenio Quarti <Silenio_Quarti> | ||||||
Status: | NEW --- | QA Contact: | |||||||
Severity: | normal | ||||||||
Priority: | P3 | CC: | b.michael, chanskw, csaszar, digga1404, eclipse, ejj-eclipsebugs, joerg.hundertmark, nathan.schile, slingn, steve_northover | ||||||
Version: | 3.0 | ||||||||
Target Milestone: | --- | ||||||||
Hardware: | PC | ||||||||
OS: | Windows 2000 | ||||||||
Whiteboard: | |||||||||
Attachments: |
|
Description
Chris Gross
2004-01-16 16:38:31 EST
Created attachment 7469 [details]
Screenshot of bug
Image transparency is not respected when used in a widget. This is a known issue. *** This bug has been marked as a duplicate of 35040 *** I'm not sure if this is actually a dupe. I was not using a PNG image in my development. It was a GIF. Futhermore, it seems the transparency WAS respected when setting the background color of the entire table. The problem occurs only when setting the background color for an individual row. revisiting SSQ is this failure unexpected? Created attachment 18113 [details]
Screen shot demonstrating image transparency problem.
I noticed a similar problem when changing the background color of my table
using ITableColorProvider. The cell highlighted in blue was highlighted with
TableCursor. In that case, the image transparency was respected. The rest of
the table coloring was done using ITableColorProvider. In that case, the
background color of the image remains the same as the default table background
color.
Hi Silenio - Any plan on fixing this for 3.1? I have a feature item depending on this bug. The feature is to allow highlighting of certain cells in the Memory View. This bug makes the highlighting very messy in the view. Thanks Samantha Hi Samantha, When I first investigate this problem, I did not find any solution. It seems that Windows will always draw the background of the image using the table background and not the row background. I will have to investigate more. Silenio any news on this bug any news on this? Is there an other solution to get round this problem ? Thank you. Steve, is there anything that can be done here? I am setting the cells image with a image (png) that has a transparent background. I am calling table.getItem(i).setBackground(colorRed); to set the rows background color. The image is getting the background color of the table rather then the row. My workaround is to use a listen to the SWT.EraseItem and set the background there. It would be nice not to have to set the background in the SWT.EraseItem, and just use the setBackground color on the TableItem. I found that when I put an icon at the left-hand end of a coloured table row in Windows, it is always surrounded by a white border (white being the background colour of the table). Windows doesn't seem to start using the row colour until a few pixels to the right of the icon. I guess this is why the transparent pixels in the icon render as white -- using the row colour wouldn't make sense. I'd like to get rid of this white area, but I haven't found a workable solution yet. The white border is a feature AKA bug 208866, see there for a workaround. 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 problem still occurs and we still want this bug fixed. We had an expert audit proofing the usability of our ecplise application. Currently there is a finding we can only solve, if this bug will be solved. Is there a chance to solve this bug in an easy and timely way? |