Skip to content

RFC: Re-brand aboutToUnbound() signal in SurfaceInterface to unbound()

Vlad Zahorodnii requested to merge work/surface-unbound into master

A compositor could use the unbound() signal to perform some cleanup, for example send a keyboard leave event, etc. When the unbound() signal is emitted, the SurfaceInterface object and the wl_surface resource are still alive so it could potentially lead to a bit more cleaner code without any paranoid nullptr checks.

Edited by Vlad Zahorodnii

Merge request reports