You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Context
ATM, when Massa Station crashes, the user has nothing to know it. The only errors are in the logs, which are not easy to access and read for most users.
Opening a window showing the error when MS crashes would help users to know that MS crashed and what is the error so they can do some researches.
User flow
Massa Station crashes
User is prompted with a dialog showing the error message
How to
When MS crashes (should be represented as a Fatal in the logger), display a dialog with the error message
Technical details
QA testing
The text was updated successfully, but these errors were encountered:
Fyne (the GUI we are using) requires to be in the main thread to open a new Window/App, which makes it impossible to open a new window/dialog from a routine
maybe another solution would be to create another binary that we will execute in another process in the fatal callback?
I thought about this solution, the issue is that we will need to build one for each platform, ship it, store it somewhere... So I feel like it's not the right thing to do
Context
ATM, when Massa Station crashes, the user has nothing to know it. The only errors are in the logs, which are not easy to access and read for most users.
Opening a window showing the error when MS crashes would help users to know that MS crashed and what is the error so they can do some researches.
User flow
How to
Fatal
in the logger), display a dialog with the error messageTechnical details
QA testing
The text was updated successfully, but these errors were encountered: