Bug 252397 - ControlExample - font label should not be enlarged (or should it?)
Summary: ControlExample - font label should not be enlarged (or should it?)
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-28 11:43 EDT by Eric Hung CLA
Modified: 2021-11-12 11:32 EST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Hung CLA 2008-10-28 11:43:40 EDT
Build ID: I20081027-1800

Steps To Reproduce:
1. Download SWT's ControlExample
2. Choose any control tab
3. select the "Font" in "Colors and Font" group
4. Click on "Change..." button
5. Change the font size to a large value, say "36"



More information:
Notice that the "Font" in the group is also enlarged
Not sure if it looks good.
Comment 1 Eric Hung CLA 2008-10-28 14:49:30 EDT
Same problem observed in CustomControls example.
Comment 2 Grant Gayed CLA 2008-10-29 12:53:04 EDT
I think the intent is to show the font that is selected, similar to the two lines above that show the selected foreground and background colours, so this seems fine.  However it does look bad when a large font is chosen, because the item height remains unchanged, and as a result the text can appear clipped on the bottom.

Car do you think it's worth adding a MeasureItem listener to the Table whenever a larger font is selected, so that the Table item height can be increased to fit the larger item text?  Of course the downside with this is that if the user then reduced the font size then the Table item height could not be decreased back as well.  Or, any other ideas?
Comment 3 Eclipse Webmaster CLA 2019-09-06 15:32:56 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.