> There is no API for the "alwaysOnTop" AWT property for the print dialogs. > I actually don't think it can be implemented for the windows native print > controls. > There is an internal way to make an AWT window owner for the Swing print > dialog > but nothing public and it doesn't help here as the owner is not an AWT window.
Ok. > > >> - Probably the name should contain «owner» instead of «parent»?, But since >> this is not a public API I guess it is not an issue. > > I suppose that is more correct. Something to address if it ever makes its way > into API or docs. > > -phil. > >> >>> >>> >>> This has an FX bug + webrev : >>> https://bugs.openjdk.java.net/browse/JDK-8088395 >>> <https://bugs.openjdk.java.net/browse/JDK-8088395> >>> http://cr.openjdk.java.net/~prr/8088395/index.html >>> <http://cr.openjdk.java.net/%7Eprr/8088395/index.html> >>> >>> and also a JDK-side fix and webrev :- >>> https://bugs.openjdk.java.net/browse/JDK-8176530 >>> <https://bugs.openjdk.java.net/browse/JDK-8176530> >>> http://cr.openjdk.java.net/~prr/8176350/ >>> <http://cr.openjdk.java.net/%7Eprr/8176350/> >>> >>> The problem is FX modal dialogs are ignoring the Window parameter. >>> We can fix the problem with disabling the modal parent on the FX side >>> and that is why most files in FX are updated. >>> >>> But it does not fix the "on top" issue which requires the JDK fixes and >>> to pass in the DialogOnTop private attribute. >>> The JDK code is there solely for FX and won't have any visibility >>> unless FX passes in the private attribute. >>> >>> On Linux it uses the standard AWT "always on top" modality >>> On windows it uses the HWND for the FX window and windows native modality >>> On Mac you won't see anything since Mac does this automatically >>> >>> -phil. >> >