You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 8, 2021. It is now read-only.
Unrelated. The problem is that delete_event is NULL here and we currently don't handle that in the subclass bindings. We would have to check for which virtual methods it is valid to have NULL there and then what the default behaviour should be (another thing for which we don't have g-i annotations...). That requires diving into the C code. I've done that for the things in gio and gstreamer, but nowhere else.
In this specific case, instead of panicking at that line it should return false here if it's NULL.
The title is wrong. It's not about handling it instead of setting to NULL, but we need to handle the parent one being NULL by implementing default behaviour.
In specific, the expect() here should be replaced by an unwrap_or(false):
alatiera
changed the title
Application subclasss needs to handle delete_event instead of setting it to NULL
Application subclasss needs to handle parent delete_event
Nov 21, 2019
Originally posted by @sdroege in gtk-rs/examples#256 (comment)
The text was updated successfully, but these errors were encountered: