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

Distinguish "build errors" from "download errors" #261

Open
PropGit opened this issue Nov 23, 2016 · 2 comments
Open

Distinguish "build errors" from "download errors" #261

PropGit opened this issue Nov 23, 2016 · 2 comments

Comments

@PropGit
Copy link
Contributor

PropGit commented Nov 23, 2016

[EDITED - see bottom of this post plus the new post]
We need Simple IDE to provide a clear distinction between a "build failure" and a "download failure."

Simple IDE currently shows the same message for both cases right now:

image

For the case shown above, when it's actually a download failure, we need the Build Error dialog to be a Download Error dialog, which says "Download Failed. Check Build Status for errors."

SimpleIDE can easily determine this result by using the -c option for PropLoader and parsing the start of messages for certain codes; Issue #260.

For example: message 005 means the download was successful, and 006 means it is now switching to terminal mode. Anything in the 100 range means the download failed (when the intent was to download, of course).

Even if not using the above technique, when there's a download error, it should still be possible to display a Download Error dialog instead of a Build Error dialog (to satisfy this issue) since SimpleIDE has already reached a distinct state where it knows it is now attempting a download.

@PropGit
Copy link
Contributor Author

PropGit commented Dec 10, 2016

@jsdenson - I edited this issue. It can still be achieved even without parsing the error codes. Please make this enhancement happen.

@PropGit
Copy link
Contributor Author

PropGit commented Dec 22, 2016

@jsdenson - Will you be readdressing this one soon?

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

1 participant