adding touch hander class as new DRV_TOUCH to enable user specific touch #64
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.
As discussed here a PR adding a new touch handler class.
The touch handler class is included as an own driver into GUIslice which can be selected as the other drivers via defines.
The user can now add a own touch driver just by performing the steps below.
Thus no modification / adoption of the GUIslice library itself is required to test / add a new touch driver.
To create a new user specific touch handler
In the user program (I have added an example arduino gslc_ex11_ard_touch_handler) just
I have successfully tested the touch handler with a STM32F1 and a 2.4" TFT SPI 240x320.
Please have I look at the text headers of the files, I did not know what has to be added.