Bug 211176 - [CCombo] problem with list component width
Summary: [CCombo] problem with list component width
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.2.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Lakshmi P Shanmugam CLA
QA Contact: Carolyn MacLeod CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-28 03:23 EST by Laura CLA
Modified: 2019-09-06 16:12 EDT (History)
2 users (show)

See Also:


Attachments
CCombo expand problem (16.27 KB, image/jpeg)
2007-11-28 03:23 EST, Laura CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Laura CLA 2007-11-28 03:23:33 EST
Created attachment 83952 [details]
CCombo expand problem

Build ID: M20070212-1330

Steps To Reproduce:
Expanding a CCombo component generates that the width of the list component is as wide as the CCombo or as wide as the widest entry in the list (whatever is wider).  
There is currently no API to control this. The size of the list is calculated in the internalLayout() method of the CCombo and this is a private method.
Comment 1 Carolyn MacLeod CLA 2009-09-17 11:21:33 EDT
We should start with the patch in bug 99718 comment 6. Then we need to figure out exactly what native Combo is doing, i.e. is it really setting the width to match the 2nd longest item string? What if there are 2 really long entries - does it use the 3rd-longest string's width? Maybe it has some other heuristic?
Whatever native Combo is doing with width seems to make people happy. So CCombo should try to emulate that. Then, I don't think we would need new API to set the list width.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:12:53 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.