-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move floating window to negative coordinates doesn't work #321
Comments
Does that even work with non-KDDW pure-Qt code ? I'm happy to support it if it's supported by Qt as well |
It should work, but there's a few snags. Can you print this (in your application, not in a testcase):
|
System: Windows 10 / VS 2019 I have observed if the floating window is only a little bit in the negative area then it won't be moved. but if the floating window is total in the negative area then the kddockwidget lib moves it to zero. Steps: Change MyMainWindow.cpp to
By the way: I suppose this is also a problem with the y axis. I didn't test it but the testcase is that the screen2 should be above screen 1so that screen 2 has negative y values. Kind Regards, Thomas |
QScreen::geometry() is already in "virtual coordinate space", no need to map again. Bug wasn't noticeable since most setups have virtual top left at 0,0, so it was a no-op in most cases. Fixes bug #321
Thanks. |
Thank you for fixing #75
But a floating window can't moved to negative coordinates.
Example: You have two monitors horizontal arranged. The right monitor is the main monitor, which means the left/top corner is the origin.
Hence the left monitor has negative X values.
If you want to move the floating window to the left monitor with this code:
floating_window>resize(size);
floating_window->move(QPoint(-250, 200);
floating_window>show();
Then the window is open at the right monitor.
And yes it is possible to switch around the code:
floating_window>show();
floating_window>resize(size);
floating_window->move(QPoint(-250, 200);
But then we have the flickering described in #75
Kind Regards,
Thomas
The text was updated successfully, but these errors were encountered: