-
Notifications
You must be signed in to change notification settings - Fork 8
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
Exception in callback breaks program #24
Comments
Hi, can you please give a short example. I'll look over it and if needed, work on a fix. There might also be a workaround depending on your use case: |
Yes, after catching the exception the program prints the error message and does not move further in the code. |
That is supposed to happen, since you should code what should happen next or if there was some mistake with recognizing the card then the card should be taken off the reader and put on it again. If you want to see a full example implementation for raising exceptions in the callback you can look at my Praesidium demo under the function The following wasn't tested so it probably doesn't work. It was just written quickly to give an overview of how it should work:
If you raise an exception in The exception in I hope i was able to clarify some things... |
issue seems to be solved - closing |
When an exception in the callback function connect(self)/disconnect(self) occurrs, the callback function never leaves and the program is stuck.
The text was updated successfully, but these errors were encountered: