[OpenJDK 2D-Dev] [9] RFR: JDK-8148431, , PrinterJob.pageDialog() does not support multi-mon, always displayed on primary

[Philip Race]

This is the same actual logic as the other bug about the print dialog.
They actually invoke the same code, just in a different mode.
We would want the logic the same I think.
I would not have filed a "new bug"  to handle this case.
I would have just added it into the existing bug.
Please close out this new bug as a duplicate and merge the two webrevs
so we can see it all at once.

-phil.

On 1/27/16, 10:27 PM, prasanta sadhukhan wrote:
> Rectified the webrev link:
>
> On 1/28/2016 11:50 AM, prasanta sadhukhan wrote:
>> Hi All,
>>
>> Bug: https://bugs.openjdk.java.net/browse/JDK-8148431 
>> <https://bugs.openjdk.java.net/browse/JDK-8148431>
>> webrev:
> http://cr.openjdk.java.net/~psadhukhan/8148431/webrev.00/
>>
>>
>> Please review a fix in continuation with JDK-8138749 . It is seen that
>> PrinterJob.pageDialog(attr set) also does not support multi-monitor 
>> setup. When this API is invoked, the page setup dialog is always 
>> displayed on the default screen device regardless of where the 
>> application is running.
>> This is because this method
>> uses ServiceDialog class for creating the dialog and that indeed 
>> supports passing a GC in which we would like to have the dialog. But 
>> printer job always uses the GraphicsConfig of the default screen device
>> resulting in page dialog to be shown on primary device/monitor.
>>
>> So, the fix is to use the GraphicsConfig of the current active window 
>> while showing the dialog.
>>
>> Regards
>> Prasanta 
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/2d-dev/attachments/20160128/9dc0b3a6/attachment.html>