On 23.09.2016 17:31, Sergey Bylokhov wrote:
On 23.09.16 17:00, Semyon Sadetsky 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.
Then this is a bug.
Why?
