Details
-
User Story
-
Resolution: Unresolved
-
P3: Somewhat important
-
None
-
None
-
None
Description
Overview
There's quite a few cases where we have methods that can fail but that do not return a status code. Since we probably can't resort to exceptions, this needs to be reviewed.
I think part of the problem was the "design for QML" mentality that went into the original design. A slot does not normally return anything.
The existing error reporting mechanism seems practically useless so it should probably just be scrapped.
Acceptance Criteria
- A solid understanding of how error reporting will work for both C++ clients and QML clients
- User stories for the implementation