Closed dsyleixa closed 5 years ago
Interesting. The Feather M4 was the first board I tested with and it seemed to be working. Do you want to update your code and submit another PR?
This has been updated.
hello, all I formerly had found from you was https://github.com/adafruit/Adafruit_HX8357_Library/issues/12#event-2296117523 and https://github.com/adafruit/Adafruit_HX8357_Library/pull/15 whilst in the Adafruit repo the TFT button example code was already 5 or 7 months old (CMIIW)
Now I tried this version (now 4 hours old): https://github.com/adafruit/Adafruit_HX8357_Library/blob/master/examples/gfxbuttontest_featherwing/gfxbuttontest_featherwing.ino and that works fine!
PS,
in the Adafruit HX8357 repo folder
gfxbuttontest_featherwing
is another extra file .mega2560.test.skip
https://github.com/adafruit/Adafruit_HX8357_Library/blob/master/examples/gfxbuttontest_featherwing/.mega2560.test.skip
what is that for?
The .mega2560.test.skp file causes the automated test for the Arduino Mega 2560 to be skipped when the code is tested. Since it was designed for a TFT FeatherWing, that was fine.
but why is that an extra file? Why is the code not integrated in the main .ino file? Finally the code is an example to work for all boards, as long as wired accordingly to either MCU board...?
PS, as to .mega2560.test.skp Why has it such a weird name? (not .ino, not .h, not .cpp, and 1 leading dot and 1 more dot in between?) Is that a Arduino code file at all? I cannot even see a single code line inside!
The dot at the beginning causes the file to be hidden. The mega2560 means it should only skip the Arduino Mega 2560 test and the test.skp is just the type of file it is. It has no usefulness other than as a way of telling the automated tests which ones to skip. Without it, all tests are run and sometimes we want to skip them.
Are the automated tests made to be used by end users? Where can I see those automated tests? OTOH, actually to me the .mega2560.test.skp file is NOT hidden in the lib.
Or can I delete this .mega2560.test.skp file from the lib if the automated tests are NOT intended to be used for end users.
If I delete it and wire accordingly to the correct Mega pins, will it work for the Mega too, or will it damage the Mega then?
Nope. They’re run whenever we submit changes to reduce the chances of breaking something. You can delete it if it bothers you. It shouldn’t damage the Mega, but it may or may not compile for it. If you’re able to get it compiling then there’s really no reason to have the skip file. It was just included as part of the pull request.
yes, it compiles for the Mega2560 cpu platform.
Awesome. thanks for letting us know.
you're welcome, I'm glad if I could help. Unfortunately some of your contributers or owners (e.g., LadyAda) are acting very unpolite and lock an issue report even if it's not resolved, so follow-up questions or remarks or updates are not possible any more. That is IMO - friendly spoken - not helpful at all, neither for your libs nor for the customers purchasing Adafruit products. Gladfully you are keeping it open until it's reported to be resolved, thank you!
@dsyleixa hiya, we cannot do tech support in github issues, if you have technical questions about why a library or hardware is designed a certain way you can ask in the forums, its not for posting in github. bug reports, code contributions only here. thanks!
well, sometimes for you it seems to be a support request at first glance, but then it turned out to be bug though. e.g. my report about SPI clock for HX8357: the freq parameter to ::begin(freq) does not represent a frequency at all, and it makes no change at all for either arbitrary value - that's definitely a bug, but I couldn't report that cause it's locked.
bug reports are welcome - if you find a bug, open a specific issue with how to reproduce it (e.g. proof of bug)
ok, then I will post th issue anew.
re: merged-in touch button example; not working for Feather M4 https://github.com/adafruit/Adafruit_HX8357_Library/issues/12#event-2296117523 (edit: regrettably this issue was locked so I could not respond there)
Thanks for merging in the touch button example https://github.com/adafruit/Adafruit_HX8357_Library/pull/15 nonetheless, my Feather M4 board could not be detected and thus the code could not be compiled because of missing board #defines and mis-spelling TFT-pin macros (partialy spelled lower-case instead of upper-case) .
Instead, this fix works for my Feather M4: