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

Quicker upload notification #279

Closed
tigoe opened this issue Mar 27, 2021 · 3 comments · Fixed by #1260
Closed

Quicker upload notification #279

tigoe opened this issue Mar 27, 2021 · 3 comments · Fixed by #1260
Assignees
Labels
conclusion: resolved Issue was resolved topic: code Related to content of the project itself type: enhancement Proposed improvement type: imperfection Perceived defect in any part of project

Comments

@tigoe
Copy link
Member

tigoe commented Mar 27, 2021

Couldn't find an issue on this one, so here goes:

  1. Open new sketch
  2. Choose board and port
  3. Click upload button

After "Compilation complete", the wait for notification about upload takes many seconds, long enough for the user to think something has gone wrong. IN that case, they might hit the reset or unplug, which disrupts the upload.

If you turn on verbose notices for upload you get

Compilation complete.
Performing 1200-bps touch reset on serial port /dev/cu.usbmodem1431301
Waiting for upload port...

Which is helpful, but the reams of text you get otherwise can be bothersome. I think it would be good to offer short "Connecing to board..." then "Uploading..." progress messages so the user knows what the status is and doesn't disrupt it.

@tigoe tigoe added the type: enhancement Proposed improvement label Mar 27, 2021
@ednieuw
Copy link

ednieuw commented Apr 23, 2021

Same annoyance. I can not see that the program is compiling or uploading.

@tigoe
Copy link
Member Author

tigoe commented Sep 5, 2021

Update using 2.0.0-beta.11

This is still unchanged. The delay is long enough that I don't feel that I can use 2.0 to teach beginners yet.

@per1234
Copy link
Contributor

per1234 commented Aug 2, 2022

Closing as resolved by #1260

@per1234 per1234 closed this as completed Aug 2, 2022
@per1234 per1234 self-assigned this Aug 2, 2022
@per1234 per1234 added the conclusion: resolved Issue was resolved label Aug 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
conclusion: resolved Issue was resolved topic: code Related to content of the project itself type: enhancement Proposed improvement type: imperfection Perceived defect in any part of project
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants