Skip to content
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

Better error handling #161

Open
vilhalmer opened this issue Nov 20, 2024 · 0 comments
Open

Better error handling #161

vilhalmer opened this issue Nov 20, 2024 · 0 comments

Comments

@vilhalmer
Copy link
Collaborator

Most VRErrors that occur are only exposed to the developer as log messages. Some of the openvr_data methods return a boolean representing success, but these are usually eaten by the XRInterface and therefore the application has no opportunity to react to a failure.

Still being pretty new to Godot, I'm not sure if there are good examples of handling errors out there that would be best to follow, so I'm filing this to get a discussion going. I would at the very least like to see VRErrors bubbled directly up to the XRInterface in some way (maybe like a last_error, so it can be used even by functions that return another type?), but translating them to a more useful form is also fine by me if one exists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant