Closed Raycast7373 closed 1 year ago
Hi @Raycast7373 Thanks for this PR. I do not have a GT911 myself so I can't be of any assistance I think regarding the issues you mentioned. I will look over the changes in the code and if everything turns out to be good to go I will merge! Thanks again!
👍👍
Adding a 3 second delay to the info page works good enough in most cases i guess (worked good enough for me)
delay(3000);
The wake on touch thing seems to not work with the gt911 You can theoretically fix it by always looking for if the touch screen is touched instead of the gpio interrupt thing (haven't looked into how it normally functions tho)
The wake on touch thing seems to not work with the gt911 You can theoretically fix it by always looking for if the touch screen is touched instead of the gpio interrupt thing (haven't looked into how it normally functions tho)
I'll have a look at the datasheet and the library. You could also check with a multimeter or oscilloscope (if you have one) what happens one that pin when you touch the screen. Also maybe there is an example in the library showing how to use the interrupt...
backlight control works after changing a small bit of code
Could you make it so that, everything you need for the GT911 is between #IFDEF's and the default still is the "normal" version for the ESP32 with resistive touchscreen?
I'll do it later today if i have time after work I'll also add a thing specifically for the ESP3248S035 capacitive touch Board me and that other person in your discord has which fixes brightness control, adds auto brightness and has everything directly working without any trouble
On Wed, Jan 11, 2023, 12:39 PM Dustin Watts @.***> wrote:
Could you make it so that, everything you need for the GT911 is between
IFDEF's and the default still is the "normal" version for the ESP32 with
resistive touchscreen?
— Reply to this email directly, view it on GitHub https://github.com/DustinWatts/FreeTouchDeck/pull/105#issuecomment-1378621181, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEXHA76GM3CK5ITFZOWJGJ3WR2LXNANCNFSM6AAAAAATPB44WE . You are receiving this because you were mentioned.Message ID: @.***>
Too exhausted,I'll do it in the weekend or smth
gonna work on it now i cant test it out right now tho cuz i left my esp32 board at home
should be good now
The compile test fails. Changed the compile.yaml but somehow it still uses the old .yaml. Even though the correct changes are visible in the .yaml file. Maybe it takes a while for it to use the updated one. Will try again tomorrow. I want it to ignore warnings for now and only fail on errors.
Well... it seems for now I can't figure out how to do this in the .yaml. I can't change -all to -error. I will do this manually and ignore this fail for now.
@Raycast7373 Sorry for this taking so long. I'm running in to (unrelated) Python issues on my Mac (which is still running an old MacOS). So I have to move to my Windows machine to test compilation and I have not had the time to do so. I haven't forgotten though and as soon as I have the time, will test compile and merge 😄
To-Do:
Only hardware that is on the Supported Hardware will be reflected in the code. PR's that add support for other boards will not be accepted. You can off course point people to your fork.
For me it is not doable to add support for all kinds of boards. Especially if I do not have the board myself.
the only problem currently is that you cant see the current config/ínformation thing cuz it somehow closes it as soon as it shows which currently is temporarily fixed using a 3 second delay