Skip to content

need `weston_binding_destroy` APIs to be public

xichen requested to merge (removed):master into master

Hi weston developers,

This MR corresponds to the email I sent to the wayland-devel mailining list. I think there are two benifits:

  1. Having the compositors to be able to create temporary bindings(used once and deleted).
  2. weston_compositor_add_*_bindings returns a weston_binding but user cannot properly destroy it.

Same reason for weston_binding_list_destroy_all. Why wouldn't libweston users have the ability to clean its binding list as it wishes.

Regards, sichem

Merge request reports