Merge lp://staging/~nick-dedekind/qtmir/miral-DisplayConfigurationStorage into lp://staging/~unity-team/qtmir/miral-qt-integration
Proposed by
Nick Dedekind
Status: | Superseded |
---|---|
Proposed branch: | lp://staging/~nick-dedekind/qtmir/miral-DisplayConfigurationStorage |
Merge into: | lp://staging/~unity-team/qtmir/miral-qt-integration |
Prerequisite: | lp://staging/~nick-dedekind/qtmir/edid |
Diff against target: |
329 lines (+169/-19) 7 files modified
CMakeLists.txt (+2/-2) debian/control (+3/-3) src/platforms/mirserver/miral/CMakeLists.txt (+1/-0) src/platforms/mirserver/miral/display_configuration_storage.h (+52/-0) src/platforms/mirserver/miral/persist_display_config.cpp (+91/-11) src/platforms/mirserver/miral/persist_display_config.h (+7/-2) src/platforms/mirserver/qmirserver_p.cpp (+13/-1) |
To merge this branch: | bzr merge lp://staging/~nick-dedekind/qtmir/miral-DisplayConfigurationStorage |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Alan Griffiths | Needs Resubmitting | ||
Review via email: mp+312693@code.staging.launchpad.net |
This proposal has been superseded by a proposal from 2017-01-25.
Commit message
Added interface for saving/loading display configuration output options.
Description of the change
Pass responsibility for display configuration storage to an overridable interface.
To post a comment you must log in.
Unmerged revisions
- 618. By Nick Dedekind
-
merged with trunk
- 617. By Nick Dedekind
-
merged trunk
- 616. By Nick Dedekind
-
merged trunk
- 615. By Nick Dedekind
-
miral 1.3.1 compat
- 614. By Nick Dedekind
-
merged trunk
- 613. By Nick Dedekind
-
merged with trunk
- 612. By Nick Dedekind
-
more info for identifying a display
- 611. By Nick Dedekind
-
print error on failed EDID parse
- 610. By Nick Dedekind
-
added check for ouput.connected to load/save config
- 609. By Nick Dedekind
-
merged parent
+ conf.for_ each_output( [this, &conf]( mg::UserDisplay ConfigurationOu tput& output) { policy. apply_to( conf);
...
default_
First apply any saved configuration and then overwrite that with the default policy. Is this the right behaviour?