<AWT Dev> [9] Review request for 8163101: dual-screen issue with JMenu, JPopupMenu

Semyon Sadetsky semyon.sadetsky at oracle.com
Fri Sep 23 14:00:58 UTC 2016

On 23.09.2016 16:51, Sergey Bylokhov wrote:
> On 01.09.16 16:41, Semyon Sadetsky wrote:
>> On 31.08.2016 21:18, Sergey Bylokhov wrote:
>>> On 31.08.16 17:18, Semyon Sadetsky wrote:
>>>> Toolkit.getDefaultToolkit().getScreenSize()
>>>> was replaced by
>>>> graphicsConfig.getBounds();
>>>> that returns a particular screen area which is not the same as the 
>>>> joint
>>>> screen area in case of Xinerama multi-monitor configuration.
>>> Can you please clarify what is the difference between two methods in
>>> this bug? Toolkit.getScreenSize() is related to the main screen
>>> only(defaul gc config), but gc.getBounds() is related to appropriate
>>> screen(and take scale factor of those screen into account). In case of
>>> xinerama we should have two GC which should have each own scales.
>> It was explained above already: they return different things.
>> Toolkit.getScreenSize() returns the whole desktop size, gc.getBounds()
>> returns particular screen bounds.
> I do not get it. Toolkit.getScreenSize() should return the size of the 
> primary screen which is default screen device in terms of 
> GraphicsEnvironment.
No, it is a whole desktop size (joint virtual screen in case of 
multi-monitor). It has been working that way always.

More information about the awt-dev mailing list