So now, between the 1st and 2nd beta is the best time to remind me about issues or pending pull requests.....
i
Possible PR to pull in:
SPI: SPI.Transfer(buf, cnt) speedup - uses queue and uses PUSHR_CONT flag to speed up multi-byte transfers (
https://github.com/PaulStoffregen/SPI/pull/23)
Wire library: Supports Wire1 on most T3.x boards, Wire2 on T3.5/6 and Wire3 on T3.6. I do this through creating a base class (TwoWire) and all of the objects are subclasses. This should make them compatible with some libraries that were modified for Arduino Due or maybe some of their newer M0 boards, which you to pass in Pointer or Reference to Wire object. Note: at least with the Due I noticed they have only one class and do the differences within the different members like begin/end... Could modify to do the same. Also currently I am using malloc to allocate main data structure as to not allocate about 80 bytes for each of these objects. I thought that might be important for boards like T-LC... But again could undo that as Serail1/Serial2... all have their static buffers... (
https://github.com/PaulStoffregen/Wire/pull/3)
ILI9341_t3 (
https://github.com/PaulStoffregen/ILI9341_t3/pull/41): Merged in some of the stuff I have in my ili9341_t3n library - A lot of this originated with some of the changes done by Blackketter did in the PR (
https://github.com/PaulStoffregen/ILI9341_t3/pull/13). In particular he added the ability to set a clip rectangle as well as a drawing origin. So I merged those into my version and tried them out and then extended them to several of the other APIs that were not covered, like some of the writeRect functions, which was more fun...
Also merged/reworked the drawFontChar code to handle Opaque - The code in PR#13, did this by adding calls to fill rect... My version does it in a similar way that drawText does with Opaque with the system font...
I believe this also pulled in some other PRs of fixing gradient fill.
Also random merge in from my library that allows the library to work with fewer Hardware SPI pins. That is will work with only 1 hardware CS pin (DC). Was needed in my library to work with SPI1 on T3.6. Also does not fail if not valid MISO pin, just disables some of the input functions... Probably not needed, but added in my library when I was doing lots of hardware testing and wondered why the program just hung
Again not sure how much if any of the ILI9341_t3 changes you want in the main library. And/or - If you wish for me to somehow add the bigger change of my library that supports the different SPI busses. Currently I do in my library using my other library SPIN