1. webbrowser launches & creates a window
2. Qt creates window on the "primary" screen - which is the first screen it ever saw. This is the phone screen.
3. Oxide reads the current screen, and the scale parameter for it: 2.25 here
4. Once the window is shown, Unity8 places the window on the external screen
5. Webbrowser & oxide get notified their window is *moved* to the external screen
6. Oxide reads the current screen, and the scale parameter for it: 1.0 now
My current suspicion is that the Oxide view isn't resizing when its screen is changed. Testing this is tough for me atm, I'm curious if a patch like
This is the current behaviour of qtubuntu:
1. webbrowser launches & creates a window
2. Qt creates window on the "primary" screen - which is the first screen it ever saw. This is the phone screen.
3. Oxide reads the current screen, and the scale parameter for it: 2.25 here
4. Once the window is shown, Unity8 places the window on the external screen
5. Webbrowser & oxide get notified their window is *moved* to the external screen
6. Oxide reads the current screen, and the scale parameter for it: 1.0 now
My current suspicion is that the Oxide view isn't resizing when its screen is changed. Testing this is tough for me atm, I'm curious if a patch like
+++ qt/quick/ oxide_qquick_ contents_ view.cc :screenChanged( QScreen* screen) { Helper( screen) ;
void ContentsView:
screenChanged
if (!proxy()) {
return;
}
proxy( )->screenUpdate d(); ->wasResized( );
+ proxy()
}
might have an impact. I hope Chris can try this out soon.