On 29.09.2016 21:55, Sergey Bylokhov wrote:
On 29.09.16 21:35, Semyon Sadetsky wrote:
This is a part of HiDPI support. The popup code should use the bounds
of the screen where it is located. It should not depend from the
method which:
- Support data for the main screen only.
- Even for this screen it returns incorrect data.
I did not get that.
The fix restores the the previous way to get screen bounds, which was
not introduced as a part of HiDPI but much earier. It had been working
before 8137571 without complains (no bugs reported).
The previous way "to get screen bounds" is incorrect, and we will get
the same bug when toolkit method will be changed.
May be it is incorrect but it is working. It is better than correct and
not working. It seems we have returned to the beginning of the
discussion. I suggest to file a new bug to investigate "the correctness"
and the necessity to fix it 9. But the current fix is must for 9.
Or did you mean it won't work in HiDPI? I tested, it works for both
HiDPI and non-HiDPI displays while the current code doesn't work for
both.
