<AWT Dev> [9] Review Request: 8148109 [SWT] Provide a supported mechanism to use EmbeddedFrame

Philip Race philip.race at oracle.com
Tue Aug 2 15:43:33 UTC 2016

OK .. I think somewhere we saw SWT code doing this on windows,
although I may be confusing it with something else. It seemed like
it was a workaround for a JDK bug.

So overall this seems fine now.

Up to you whether you deal with a note on hi-dpi in this change
or separately since as you point out it applies to extant methods too ..


On 8/2/16, 8:36 AM, Sergey Bylokhov wrote:
> On 02.08.16 18:28, Philip Race wrote:
>> Ok, so when you wrote :
>>  - On OSX validateWithBounds() intentionally was changed to
>> setBoundsPrivate() as on other platforms.
>> where should I see that change ?
> In the CViewEmbeddedFrame we have two methods setBoundsPrivate() and 
> validateWithBounds(). Currently on OSX the SWT library use 
> CViewEmbeddedFrame.validateWithBounds() (this method also validate the 
> frame and make it visible). In the jawt api I use setBoundsPrivate() 
> and skip validateWithBounds, so validate+setVisible should be called 
> by the client of jawt API. (like on other platforms win/lin). I am 
> actually not sure that it is necessary to call validate here.

More information about the awt-dev mailing list