From cb593883537c2e55897ef2f9e1a6cddd62cb761a Mon Sep 17 00:00:00 2001 From: Bodmer Date: Mon, 6 Jan 2020 22:28:30 +0000 Subject: [PATCH] Amend --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 4e6b862..735d09c 100644 --- a/README.md +++ b/README.md @@ -5,11 +5,11 @@ If you load a new copy of TFT_eSPI then it will over-write your setups if they a ``` You must make sure only one setup file is called. In the the custom setup file I add the file path as a commented out first line that can be cut and pasted back into the upgraded User_Setup_Select.h file. The ../ at the start of the path means go up one directory level. Clearly you could use different file paths or directory names as long as it does not clash with another library or folder name. -You can take this one step further and have you own setup select file and then you only need to replace the Setup.h line reference in User_Setup_Select.h to, for example: +You can take this one step further and have your own setup select file and then you only need to replace the Setup.h line reference in User_Setup_Select.h to, for example: ``` #include <../TFT_eSPI_Setups/my_setup_select.h> ``` -To select a new setup you then edit your own my_setup_select.h file. +To select a new setup you then edit your own my_setup_select.h file (which will not get over-writtem furing an upgrade). # News 1. A new beta test branch has been added to support other processors, in particular STM32: