I disapprove of this design. A surface manager should not care about display state. It's the shell's decision if a client surface should be marked invisible when the display is off.
Also this throws away any visibility state that the shell may have set on surfaces.
A remote desktop would be an example where we don't care about the actual display state.
void MirSurfaceManag er::displayOff( ) er::displayOn( )
void MirSurfaceManag
I disapprove of this design. A surface manager should not care about display state. It's the shell's decision if a client surface should be marked invisible when the display is off.
Also this throws away any visibility state that the shell may have set on surfaces.
A remote desktop would be an example where we don't care about the actual display state.