|interface Efl.Layout.Signal |├ (M) message_send |├ (M) signal_callback_add |├ (M) signal_callback_del |├ (M) signal_emit |├ (M) signal_process
The alternative would be to add explicit methods for signal handling, the names of which would likely conflict with layout signal method naming and guarantee naming conflicts for any case where both classes/interfaces are brought into the same hierarchy.
I think we might have a problem with this API. The callback is defined as an opaque type that will require binding to implement manually. I think we might want to changed things here and have a legacy call that is not residing in .eo with the old legacy callback API function prototype and a new API using Eo callback so that binding can generate this one automatically. I think it is doable and shouldn't be a big amount of work. If you want to assign that work to me, I might be able to do it tomorrow.