Open hasufell opened 7 years ago
You can try G_SIGNAL_MATCH_ID
while signal_id
acquired by g_signal_lookup
Or use glib::signal::signal_handler_block
with i64
returned by connect_toggled
You can try G_SIGNAL_MATCH_ID while signal_id acquired by g_signal_lookup
Doesn't work with g_signal_handlers_block_matches()
though:
Passing at least one of the G_SIGNAL_MATCH_CLOSURE, G_SIGNAL_MATCH_FUNC or
G_SIGNAL_MATCH_DATA match flags is required for successful matches.
Or use glib::signal::signal_handler_block with i64 returned by connect_toggled
That's certainly an option right, but g_signal_handlers_block_matches()
allows more fine-grained matching, no?
Then seems really no way to use this function.
I see no useful way to invoke
gobject_sys::g_signal_handlers_block_matched()
.The gnome documentation suggest I either need
G_SIGNAL_MATCH_CLOSURE
,G_SIGNAL_MATCH_FUNC
orG_SIGNAL_MATCH_DATA
as GSignalMatchType for any match to occur.I don't see any way to provide either of those information, because of the way the gtk bindings connect to signals, utilizing rust closures I have no access to: