-
Notifications
You must be signed in to change notification settings - Fork 15
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
Completion of error handling #3
Comments
Thanks very much for pointing this out, will fix shortly. |
Actually, a large number of functions used are capable of failing, and there is little code in-place to handle it. I'll be more than happy to help you out with this if you would like. |
@sdhand, there are two distinct types of calls that we can make for any server request - in general a checked and unchecked type. https://xcb.freedesktop.org/manual/structxcb__generic__error__t.html and, it seems that we aren't doing very much on the event loop. So, I'm wondering if you would prefer we swap over to all of our calls being checked calls, so that we can immediately handle errors should they arise with the use of a follow up call - or if you'd like to just use a pass/fail approach to a call and lose the ability to narrow down errors? |
Save for event, naturally |
Would you like to add more error handling for return values from functions like the following?
The text was updated successfully, but these errors were encountered: