Details
-
Epic
-
Resolution: Unresolved
-
Not Evaluated
-
None
-
None
-
None
-
Reveal the error on player
Description
What is the benefit? Why is this valuable?
QML is error prone and can break easily. If there is error on the QML, the player does not show anything and thus is hard to find the root cause for the user.
What are common use cases?
Any UI creation, really
Technical information
When QML is broken and player cannot start, DS needs to open the APPPLICATION OUTPUT window automatically and show the error to the user. Stretch goal: If the user clicks the error text/link it should pinpoint to the source.
- proper output pane (task exists)
4.6: Errors to be displayed for user so they can fix their project.