<Swing Dev> <AWT Dev> [8] Review Request: JDK-8027157 [SwingNode] needs explicit expose for JWindow
Anton V. Tarasov
anton.tarasov at oracle.com
Fri Oct 25 13:45:30 UTC 2013
Hi Artem,
On 10/24/13 6:59 PM, Artem Ananiev wrote:
> Hi, Anton,
>
> it looks much better now. Is it possible to create a regression test
> for this change?
Ok, I did that. Here's the test:
http://cr.openjdk.java.net/~ant/RT-32570.test/webrev.0
It persistently passes with the fix (Window/Mac), and fails without
(Windows).
I'll push it to jfx8 right after this fix gets into jdk8 and jfx8 is
switched to build since that jdk8 build (if that is possible).
Thanks,
Anton.
>
> Thanks,
>
> Artem
>
> On 10/24/2013 6:35 PM, Anton V. Tarasov wrote:
>> Hello,
>>
>> Please look at the new version:
>>
>> http://cr.openjdk.java.net/~ant/RT-32570/webrev.1
>>
>> It eliminates code dependency b/w awt & swing.
>>
>> Thanks,
>> Anton.
>>
>> On 10/23/13 10:15 PM, Anton V. Tarasov wrote:
>>> Hello,
>>>
>>> Please, review the fix:
>>>
>>> jira: https://bugs.openjdk.java.net/browse/JDK-8027157
>>> webrev: http://cr.openjdk.java.net/~ant/RT-32570/webrev.0
>>>
>>> This is to support SwingNode. On Windows, in the interop mode, when a
>>> popup (JWindow) is shown it doesn't get WM_PAINT native message.
>>> The message should trigger adding a dirty component to RepaintManager
>>> that will eventually paint it.
>>> Currently, a popup is shown blank. Please, see
>>> https://javafx-jira.kenai.com/browse/RT-32570 for more details.
>>>
>>> The fix explicitly calls for WWindowPeer.handleExpose(..) on showing a
>>> window owned by JLightweightFrame.
>>>
>>> Thanks,
>>> Anton.
>>
More information about the swing-dev
mailing list