On the one hand I wish Peter maintained his repo in something resembling a standard git way, on the other he is pretty responsive to bug reports. So, if I had to pick I’d take what we have.
1 Like
I just synced the repo with my fork and I’ll get a release out in a bit. Looked like there might have been a few other minor fixes too in there. Also sounds like based on the continued conversation over there, this will end up being the final release.
Hopefully having the fork for PicoCalc helps. It was bumpy at first trying to get the initial patch code for the first PicoCalc release from guu/Clockwork synced up and working properly with the newer version of the PicoMite code. While comments from the upstream repo are basically nonexistent, at least the changes do come in chunks organized around certain features or bugfixes. I’m not sure as a user that I’d want to ever try to keep up with the bleeding edge version that was just released though, since things change frequently and bugs are introduced and fixed quite rapidly. I’d think for actually using it to write code it would be much better to go with a stable version that was documented and a known quantity. The problem with the PicoCalc was that it released during an ongoing development cycle, and shipped with a much older version of the code that had its own issues, along with new issues because of the specific PicoCalc hardware that wasn’t fully supported. There are still a few things I’d like to clean up and do with the PicoCalc version, but hopefully one based on the final 6.00.02 version will be able to satisfy most people for a good long while until the next new main version is near ready for release.
For PicoCalc specifically, I’m probably going to have another version or two after the final mainline one, to pick up some additional things specific to PicoCalc like setting display brightness, the options issue on guthub, and probably a few other minor things and cleanup.
2 Likes