> 1. Is it worthwhile having both mutable and immutable MirTouchscreenConfig?
We have a non const / const API for all configurations. Touchscreen is not different or special in that reguard.
> 2. Are we confident this API won't ever change? (If it might change then it > ought to be accessed via the extensions mechanism.)
« Back to merge proposal
> 1. Is it worthwhile having both mutable and immutable MirTouchscreenC onfig?
We have a non const / const API for all configurations. Touchscreen is not different or special in that reguard.
> 2. Are we confident this API won't ever change? (If it might change then it
> ought to be accessed via the extensions mechanism.)