Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 356472 - [10.7] Bad sizing of ProgressBar
Summary: [10.7] Bad sizing of ProgressBar
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.8   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-01 09:34 EDT by Markus Keller CLA
Modified: 2020-03-18 16:29 EDT (History)
3 users (show)

See Also:

Attachments
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 Markus Keller CLA 2011-09-01 09:34:01 EDT 
I20110830-1241 cocoa 32bit on Mac OS X 10.7

The sizing of ProgressBar widgets is not good on Lion.

In the ControlExample with "Preferred" size, the progress bar looks taller than e.g. in the Finder's copy dialog or in Disk Utility > First Aid > Verify Disk.

Furthermore, with the "Preferred" size, the top and bottom border lines are cut off (compare this to e.g. "100 X 100").

-Dorg.eclipse.swt.internal.carbon.smallFonts doesn't make a difference.
Comment 1 Markus Keller CLA 2011-09-01 13:16:45 EDT 
I just realized that the Software Update's progress bar is as tall as the SWT one, so there seem to be multiple OS "defaults". I still prefer the small version (at least when the smallFonts property is set).

Nevertheless, the Preferred size should still not cut the borders.
Comment 2 Eclipse Genie CLA 2020-03-18 16:29:19 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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 automated Eclipse Genie.