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
When working with the chip-kit extension for arduino, the pic32prog program is called to program the PIC. The code for this can be seen here to emit backspace characters to the console, to emulate a progress bar. This tool is configured using these lines
Unfortunately, the arduino console shows these characters as backspace symbols, rather than moving the document insertion point back to the start of the progress bar.
If this were changed in core, it would probably need to be here
Which of this are reasonable approaches to fixing this behaviour?
Use a full console-emulator inside the arduino IDE
Implement handling of \b and \r, and hope nothing else is really needed?
Modify picprog binary to produce \b-free output?
The text was updated successfully, but these errors were encountered:
Note that the program will print a line of ., then use \b to move the cursor back to the first dot, and then overwrite each dot with # while the upload progresses. I'm actually a bit surprised about this, I would have expected a backspace character to actually erase the previous character, rather than just moving the cursor back, but maybe this is not how regular terminals work...
When working with the chip-kit extension for arduino, the
pic32prog
program is called to program the PIC. The code for this can be seen here to emit backspace characters to the console, to emulate a progress bar. This tool is configured using these linesUnfortunately, the arduino console shows these characters as backspace symbols, rather than moving the document insertion point back to the start of the progress bar.
If this were changed in core, it would probably need to be here
Which of this are reasonable approaches to fixing this behaviour?
\b
and\r
, and hope nothing else is really needed?picprog
binary to produce \b-free output?The text was updated successfully, but these errors were encountered: