Better error handling and notification

Open xusheng6 opened this issue 3 years ago • 1 comments

Right now, things work well if they work. When they fail, they tend to fail silently. We should let the user know what has failed and why. Two improvements are needed:

For operations that can fail, e.g., launching, stepping, etc, check whether the operation succeeds. When it fails, make sure we either set the status text or do a LogWarn, so the user can know about it. Also, make sure the UI is in a sane state after the failure.
Refactor the API to use a struct to return both a boolean value and an error string. When the operation fails, the error string can help explain why.

Related to: https://github.com/Vector35/debugger/issues/139

Apr 22 '22 06:04 xusheng6

Blocked on #172. If I deal with this issue right now, once #172 is landed, much of the effort would be wasted

May 09 '22 03:05 xusheng6