Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TTGO Display] Plugin for TTGO Display #3961

Closed
wants to merge 4 commits into from

Conversation

kretzp
Copy link
Contributor

@kretzp kretzp commented Feb 19, 2022

[TTGO Display] Plugin for TTGO Display tu use the on board display

[TTGO Display] Plugin for TTGO Display tu use the on board display
@kretzp
Copy link
Contributor Author

kretzp commented Feb 19, 2022

I wrote a Plugin for TTGO DUisplay based on your Plugin Plugin 095: ILI9341 TFT 2.4inches display
photo_2022-02-19_14-35-41 (2)

@tonhuisman
Copy link
Contributor

tonhuisman commented Feb 19, 2022

The ST77xx series of TFT chips is already supported via plugin P116, in PR #3761, without pulling in the massive and inflexible (compile-time configuration) eTFT library...
And also, plugin ID P126 is already reserved for the FT6206 touch controller, as can be seen in (pinned) issue #3839

Edit:
And via #3903 support for other ILI934x and ILI948x TFT is made available by extending P095.

@TD-er
Copy link
Member

TD-er commented Feb 19, 2022

Not sure what to think about this PR.
The code in P126_data_struct.h does look so familiar, that even the comments make me think a lot of it is a copy/paste from another plugin.

This also means that the code to decode commands has a lot of overlap with existing code, thus increasing the build size as it cannot be re-used.

I leave it to Ton to look into this, as he's also been working a lot on the (pending) PRs for other displays.

@TD-er TD-er added the Status: Needs Info Needs more info before action can be taken label Feb 19, 2022
@tonhuisman
Copy link
Contributor

I can only suggest to drop this PR, as it is, as stated in the OP, a carbon copy of P095, reworked for the TTGO unit, that was even used for bug-fixing of the P116 code, starting here, implying that this is not a feasible PR.
Another red flag is the use of the TFT_eSPI library, that is fine for any Arduino, single purpose, implementation, but 'less suitable' for integration in ESPEasy, as it is configured by handcrafting .h files, and recompiling.

The duplication of the command handling I mitigated by implementing the AdaGFX_Helper, that processes the commands for P116, P095 and P096, and can handle any new display plugin that is based on Adafruit_GFX. It also de-duplicates most of the settings on the Device configuration page, that otherwise would have to be repeated for each display plugin.

@TD-er
Copy link
Member

TD-er commented Feb 19, 2022

Closing as it is essentially a duplicate of a pending PR: #3761
Also the chosen library is very hard to use in ESPEasy, as Ton mentioned, since the library needs to use defines at compile time to setup parameters.

@TD-er TD-er closed this Feb 19, 2022
@kretzp
Copy link
Contributor Author

kretzp commented Feb 20, 2022

OK, I didn't see, that you are already working on P116. If you don't mind i will test #3761 with my TTGO Display and give you feedback...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Info Needs more info before action can be taken
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants