arpruss
arpruss
This could lead to a really hard to find bug on a device with 256k flash and a large sketch. Maybe one could define something based on the upload.maximum_size field...
Here's what I am thinking: In platform.txt, for both c and c++ building, add: -DARDUINO_UPLOAD_MAXIMUM_SIZE={upload.maximum_size} Then in EEPROM.h we can put: #define FLASH_SIZE \ ( ARDUINO_UPLOAD_MAXIMUM_SIZE > 768*1024 ? 1024*1024...
I'm still not used to modern compilers and being able to count on them to optimize all complex constant expressions away. Yes, one could put it in a const variable....
I put in a PR that handles this issue (from a different github username, for my convenience).
Lots of work would need to be done. I would recommend starting with my raspberryjammod project which at least supports 1.9.
If you're on Windows, you can press ctrl-alt-del, start the Task Manager and kill the python process. If you're on Linux or OS X, you can pull up a terminal...
May I make a suggestion? getBlocks() is not all that useful on its own. What would be really useful would be a getBlocksWithData() command. So maybe both getBlocks() and getBlocksWithData()...
I really don't know, either, sorry.
I just looked at the Juice source code. They first loop y, then x, then z. Also, for reasons of compatibility with Jam, can you separate the values between different...
In my Raspberry Jam Mod repository, there is now a binary blob zip file of the scripts for python2 and another for python3. While I'm developing with python2, from now...