Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 302248 - SWT Table: Header is not rendered at certain position for many columns
Summary: SWT Table: Header is not rendered at certain position for many columns
Status: CLOSED DUPLICATE of bug 72293
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.0   Edit
Hardware: PC Windows XP
: P3 major with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-09 05:26 EST by Christoph Sieb CLA
Modified: 2012-02-13 17:22 EST (History)
2 users (show)

See Also:

Attachments
Plugin Project with a SWT Table reproducing the problem (7.25 KB, application/octet-stream)
2010-02-09 05:29 EST, Christoph Sieb 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 Christoph Sieb CLA 2010-02-09 05:26:12 EST 
Build Identifier: M20090211-1700

In case there are many columns in a SWT Table widget, at a certain position the column headers are not rendered any more. The problem occurs for many columns. This problem is quite sever, as no workaround exists.


Reproducible: Always

Steps to Reproduce:
1.Create a SWT Table widgedt (tested within an eclipse plugin, not stand alone)
2.add at least 400 columns with a dummy column name and add some dummy rows
3.start the plugin and scroll to the right
4.at a certain position the column headers are not rendered any more.
Comment 1 Christoph Sieb CLA 2010-02-09 05:29:32 EST 
Created attachment 158571 [details]
Plugin Project with a SWT Table reproducing the problem

You can import this plugin project and start it to reproduce the table column header problem
Comment 2 Felipe Heidrich CLA 2010-02-09 09:27:15 EST 
I believe this is a limitation in win32.
Comment 3 Silenio Quarti CLA 2012-02-13 17:22:11 EST 

*** This bug has been marked as a duplicate of bug 72293 ***