1. run an "internal client" in qtmir/miral
2. use mir_connection_set_display_config_change_callback() to monitor display configuration changes.
3. this can use the client API mir_connection_set_base_display_config() to apply a saved configuration
Pros: simple to implement using established libmirclient API
Cons: can't react to (e.g. h/w) changes before a new config has been applied
Is this worth doing as a first cut implementation?
Current "strawman" implementation idea:
1. run an "internal client" in qtmir/miral set_display_ config_ change_ callback( ) to monitor display configuration changes. set_base_ display_ config( ) to apply a saved configuration
2. use mir_connection_
3. this can use the client API mir_connection_
Pros: simple to implement using established libmirclient API
Cons: can't react to (e.g. h/w) changes before a new config has been applied
Is this worth doing as a first cut implementation?