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

Pipeline exception handling #30

Open
micheljansen opened this issue Aug 5, 2010 · 3 comments
Open

Pipeline exception handling #30

micheljansen opened this issue Aug 5, 2010 · 3 comments

Comments

@micheljansen
Copy link
Member

It should stop processing on an unhandled exception, rather than keep going as is now the case.

@micheljansen
Copy link
Member Author

Exceptions that occur are handled now. Only problem is that it's not possible to show (helpful) OpenCV errors without making the scheduler dependent on OpenCV.

@raloos
Copy link
Member

raloos commented Aug 8, 2010

We could introduce a OpenCVProcessor which inherits from PipelineElement to catch these exceptions automatically without making the scheduler dependent on OpenCV. Not very pretty. The alternative is to make the scheduler include opencv/cv.h which is also not very pretty, but since such a large part of the program depends on OpenCV it might be worthwhile?

@micheljansen
Copy link
Member Author

I'm not sure which is better. The first one incurs extra burden on the programmer (must remember to extend the right one), the second one adds a dependency on opencv to the framework (so it will no longer compile without opencv, even if we refactor the opencvcamera and processors into plugins).

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

No branches or pull requests

2 participants