Skip to content

Make RegionInterface private

Vlad Zahorodnii requested to merge work/private-region-interface into master

If a Wayland protocol deals with regions, they will be exposed as QRegion objects in public API. Therefore, it makes sense to make RegionInterface private as it's an implementation detail and it's not intended to be used in public api.

The corresponding test was dropped because the CompositorInterface no longer emits a signal to indicate that a wl_region has been created. It should be also noted that wl_region stuff is already tested via other means, e.g. surface damage, etc.

Merge request reports