Good that you got it working. Was the solution to surround the header file names with < > instead of " " ?

After spending days from scratch to a working installation I have written up a guide, which I will update, and made it available on GitHub. It covers many common problems and solutions that can be very hard to find by Internet searching. It's not definitive, and it's not finished, but hopefully it w...

After spending days from scratch to a working installation I have written up a guide, which I will update, and made it available on GitHub. It covers many common problems and solutions that can be very hard to find by Internet searching. It's not definitive, and it's not finished, but hopefully it w...

After spending days from scratch to a working installation I have written up a guide, which I will update, and made it available on GitHub. It covers many common problems and solutions that can be very hard to find by Internet searching. It's not definitive, and it's not finished, but hopefully it w...

I assume you have run BUILD and restarted VSCode? The red squiggles often disappear then. Also tft.h and tftspi.h are in the folder tft so perhaps you don't need to specify the folder, could you try just #include "tft.h" and #include "tftspi.h".

Yes I see your point Jakub, I will take your advice and just leave it. I'm afraid I am one of those people that don't like to see any messages that suggest something could be fixed!
Thank you for your help
Steve

Thank you for the comments Jakub; I pleased that all should be OK despite the warning message. I seem to have Python in the following locations: e:\ESP_tool>where python C:\Program Files\Python312\python.exe C:\Users\Steven\.espressif\python_env\idf5.2_py3.12_env\Scripts\python.exe C:\Users\Steven\A...

After spending days from scratch to a working installation I have written up a guide, which I will update, and made it available on GitHub. It covers many common problems and solutions that can be very hard to find by Internet searching. It's not definitive, and it's not finished, but hopefully it w...

After spending days from scratch to a working installation I have written up a guide, which I will update, and made it available on GitHub. It covers many common problems and solutions that can be very hard to find by Internet searching. It's not definitive, and it's not finished, but hopefully it w...

I had the same problem and many other obstacles to overcome, so for my benefit I wrote a step-by-step guide, which I have attached - I hope it's useful, it's not finished so I'll add updates when I can.