Iām not trying to rush you. Certainly, take all the time you need. We appreciate your stepping up to keep the latest and greatest version on PicoCalc. Thank you, Ernst!
Lately I have been working on my build procedure, this is the first time that I do not have the uf2 files in the zip archive. Also all images, except final, display an additional banner to remind that you are not running the final release version.
Difficult to test editor F10 saving on large files as most of my programs generate āline too longā errors at some point . I did notice it scroll past the bottom of the screen though when highlighting and saved 900 bytes or so of a programā¦
One of my programs weirdly refuses to accept ctrl-c now !?, I can access it though by entering āedit "magaccā
Do you have OPTION CONTINUATION LINES in your option list? If not, thatās the reason youāre getting the line too long error. If you add that line, then, when typing a line thatās longer than one screen line, type the line up to the 38th character. Then type a space in the 39th character and an underscore in the 40th. Then hit enter and continue typing the line on the next line. If your line is longer than 80 characters, repeat the process on the second screen line to create a 3rd screen line.
@ernst , what does the āsdtest_v1.0.uf2ā file do? I assume it tests the SD card, but is the test destructive? What information does it provide?ā¦.thxā¦.Brian
It is something I need and is not destructive, it tries to create a file and then tries to delete the file, with varying clock speed. It is harmless. You can find the explenation here.
Using Pico2 ?
Please try to nuke and reflash. I have been noticing problems with I2C that I am still chasing, I am using the Pico2 B1 version on the PicoCalc without noticeable problems on the keyboard.
I just checked the source and the keyboard routine is unchanged from B0, but will change in the near future handle return codes properly instead of ignoring.
If you selected more than a certain number (the exact number escapes me now) of characters in the editor then the editor would start acting weird. The problem is gone now, though.