-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introspection does not detect most error domains #109
Comments
I'm not quite sure if it's the cause of this issue, but it's worth noting that corresponding |
Is it because the GUsbDevice error uses |
That's plausible but would be pretty odd; As an aside, I'm currently using a manually modified VAPI file on my end to work around this issue. |
Can you share what you're adding? I see
|
All I do is replace |
@v1993 If you can work out the fix I'm happy to review and then tag a new release. |
I'm currently bundling a modified vapi file with my application, which is good enough to get it working; hopefully will look into a proper fix later. |
As of right now, only
SourceError
is properly declared as an error in generated files (see e.g. valadoc). This is a big issue for language bindings, since it removes the ability to (nicely) selectively catch exceptions from GUsb.The text was updated successfully, but these errors were encountered: