Bug 87141 - [TableEdtior] does not paint over cell image
Summary: [TableEdtior] does not paint over cell image
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Duong Nguyen CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-04 09:44 EST by Richard Birenheide CLA
Modified: 2019-09-06 16:09 EDT (History)
2 users (show)

See Also:


Attachments
Proposal for changed TableEditor (2.61 KB, text/plain)
2005-03-04 09:46 EST, Richard Birenheide CLA
no flags Details
Proposal for changed TableEditor (2.65 KB, patch)
2005-03-04 09:58 EST, Richard Birenheide CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Birenheide CLA 2005-03-04 09:44:26 EST
Using org.eclipse.awt.custom.TableEditor, the Control, which is assogned as 
editor, is not drawn across the image part of the cell but only the text part. 
For certain editors, like text editors, drop down boxes or the like, this might 
be a desired behaviour, for others like checkboxes who can express their value 
only by an image, this is not. Ideally, this behaviour should be possible to be 
altered columnwise (as to say that one can specify for which columns the 
editor's Control should be drawn across the image of the cell and for which 
not) but at least this should be specifiable for the editor as a whole.
Comment 1 Richard Birenheide CLA 2005-03-04 09:46:12 EST
Created attachment 18459 [details]
Proposal for changed TableEditor
Comment 2 Richard Birenheide CLA 2005-03-04 09:58:25 EST
Created attachment 18460 [details]
Proposal for changed TableEditor
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:09:01 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.