Adapt TFT_eSPI integrated touch to use raw capture #143
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Address touch rotation issue from #141 - DRV_TOUCH_TFT_ESPI use TFT_eSPI's raw touch APIs and leave dynamic rotation and calibration to GUIslice
This was referenced Jun 4, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adapt TFT_eSPI integrated touch to use raw capture
DRV_TOUCH_TFT_ESPIuse TFT_eSPI's raw touch APIs and defer dynamic rotation and calibration to GUIslice. TFT_eSPIgetTouch()API (with its own calibration) is no longer used.esp-tftespi-default-xpt2046_intdiag_ard_touch_calib) now supportsDRV_TOUCH_TFT_ESPImode