Merge lp:~alan-griffiths/miral/monitor-outputs into lp:miral
| Status: | Merged |
|---|---|
| Approved by: | Gerry Boland on 2016-07-22 |
| Approved revision: | 245 |
| Merged at revision: | 230 |
| Proposed branch: | lp:~alan-griffiths/miral/monitor-outputs |
| Merge into: | lp:miral |
| Diff against target: |
708 lines (+644/-1) 8 files modified
include/miral/active_outputs.h (+73/-0) include/miral/output.h (+113/-0) include/miral/window.h (+1/-1) miral/CMakeLists.txt (+2/-0) miral/active_outputs.cpp (+131/-0) miral/output.cpp (+118/-0) test/CMakeLists.txt (+1/-0) test/active_outputs.cpp (+205/-0) |
| To merge this branch: | bzr merge lp:~alan-griffiths/miral/monitor-outputs |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Gerry Boland | 2016-07-21 | Approve on 2016-07-22 | |
|
Review via email:
|
|||
Commit Message
Introducing ActiveOutputsMo
| Alan Griffiths (alan-griffiths) wrote : | # |
> "Outputs" is replacing "Display"? /me ambivalent, but your team may have
> stronger opinions :)
I guess I'll ask.
...
> +++ miral/output.cpp
> +auto miral::
> bool
> I'm fine with this for a first cut. For later I'd prefer operations like
> orientation or resolution change just cause an output update, not an
> add/remove.
I don't see the connection between the code and your comment. For the latter, see
ActiveOutputs.
> + if (lhs_bad || rhs_bad) return lhs_bad == rhs_bad;
> if both outputs bad, this returns true. Are 2 invalid outputs equivalent?
IMO They have equivalent display areas.
- 240. By Alan Griffiths on 2016-07-22
-
merge lp:miral
- 241. By Alan Griffiths on 2016-07-22
-
for_each_output() is a more consistent name
- 242. By Alan Griffiths on 2016-07-22
-
Oh for a standard Units library
- 243. By Alan Griffiths on 2016-07-22
-
Fix typo
- 244. By Alan Griffiths on 2016-07-22
-
Consistency
- 245. By Alan Griffiths on 2016-07-22
-
re-sync working copy
| Alan Griffiths (alan-griffiths) wrote : | # |
> > "Outputs" is replacing "Display"? /me ambivalent, but your team may have
> > stronger opinions :)
>
> I guess I'll ask.
Actually, the Mir codebase uses output too. E.g. DisplayConfigur

+++ include/ miral/active_ outputs. h stener update_ output( Output const& updated, Output const& original);
+class ActiveOutputsLi
+ virtual void advise_
this is great to have, thank you
"Outputs" is replacing "Display"? /me ambivalent, but your team may have stronger opinions :)
+class ActiveOutputsMo nitor outputs( std::function< void(std: :vector< Output> const& outputs)> const& functor) const; output( functor) style usually, has that been changing?
+ void process_
Mir uses the for_each_
+++ include/ miral/output. h
+ /// The physical size of the output.
+ auto physical_size() const -> PhysicalSize;
What units? mm?
+ auto orientaton() const -> MirOrientation;
Typo
=== modified file 'miral/ CMakeLists. txt' miral/active_ outputs. h
+ active_outputs.cpp ../include/
use ${CMAKE_SOURCE_DIR} for consistency
+++ miral/output.cpp equivalent_ display_ area(Output const& lhs, Output const& rhs) -> bool
+auto miral::
I'm fine with this for a first cut. For later I'd prefer operations like orientation or resolution change just cause an output update, not an add/remove.
+ if (lhs_bad || rhs_bad) return lhs_bad == rhs_bad;
if both outputs bad, this returns true. Are 2 invalid outputs equivalent?