Tag: Branch: Tree: 95a267d582

wilder

wilder-5.14

wilder-5.17

wilder-5.18

wilder-5.19

wilder-5.22

wilder-5.24

wilder-5.25

wilder-5.26

wilder-5.26-rebase

wilder-broken-krunner

wilder-portage

wilder-portage-prov

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '95a267d582'

${ noResults }

Commit Graph

4 Commits (95a267d582ba041bbc245b7a22adc7af42e3ffa3)

Author	SHA1	Message	Date
Marco Martin	9c04d56236	Delay setPrimaryOutputName on X11 nativeeventfilter ... if we do immediately setPrimaryOutputName, the name is still :0.0 because the app didn't have time to react yet (since here we are in the event filter, we are just before that by definition) so the output name can still be wrong. when we go from no outputs to one, at this point the name of the one QScreen instane is still wrong :0.0 which will be renamed right after. BUG:447936	4 years ago
Marco Martin	03d37ed804	Consider fake outputs as not existent ... when we disconnect all real outputs, we only have a single fake QScreen in this case consider corona to not have screens and remove all desktops and panels. makes easier for a coherent reconstruction when real screens get back and won't save in screen mapping the :0.0 connector name	4 years ago
Aleix Pol	468a59cbb3	shell: Make sure the primary output is initialised on X11 as well ... BUG: 445589	4 years ago
Aleix Pol	0f2be58f14	shell: Add support to wayland primary outputs ... Refactors XRandr support together with the new Wayland code into a PrimaryOutputWatcher class. For X11 it listens to xcb events. For Wayland it uses the kde_output_management_v2 protocols.	4 years ago