JDK-6497781 : Should use Prop.CONTENTMARGINS instead of Prop.SIZINGMARGINS
- Type: Bug
- Component: client-libs
- Sub-Component: javax.swing
- Affected Version: 6
- Priority: P3
- Status: Closed
- Resolution: Duplicate
- OS: windows_xp
- CPU: generic
- Submitted: 2006-11-28
- Updated: 2010-04-02
- Resolved: 2007-06-29
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 7 |
|---|
7Resolved  |
Related Reports
|
Duplicate :
|
|
|
Relates :
|
Description
In XPStyle we use Prop.SIZINGMARGINS to find component margins. SIZINMARGINS has nothing to do with it. It is about how to stretch a part image and is used by the system. We should be using Prop.CONTENTMARGINS instead.
Comments
|