I have the simulator running in Visual Studio. I have ported LVGL to the Teensy (IMXRT1062DVL6) and ILI9488/XPT2046. Everything was working great in LVGL v7 but I made the mistake of upgrading…
I’m not a sophisticated programmer; I hoped the first “L” in LVGL meant I could easily and quickly develop a user interface but I am experiencing constant, sustained frustration. Here’s why…
demo_widgets is great because it uses every possible LVGL feature. But to get back to a blank project is extremely difficult – things have to be understood and then carefully pruned (and short, /**/ comments confound commenting out big blocks. )
So I tried creating a new project – HUGE challenge! I’ve spent hours and can’t figure out how to satisfy both VS and LVGL – what include files to use, C++ issues, file locations etc. 3/4 of VS errors just don’t make sense.
If I copy the code in one of the excellent examples (at Examples — LVGL documentation ) into VS, it’s the same set of complex issues – where should the file live? What includes do I need? How do I include the file in my project? I’d like a simple guide that shows me how to take an example and build it in Visual Studio. Or maybe I need to ditch VS and go CodeBlocks? I just need a pathway to get this miserable job done!
Thanks for making this great tool. Please help me put it to use.
Welcome back. VS is universal IDE and setup is as you see …
Try use Platformio in it , here all you need is one ini file…
I want to answer my own question. First, thanks Marian_M but I haven’t tried Platformio yet – that seems like more complication – a way to stay in VS, whereas, because I’m using Teensy, I want to develop embedded code in the Arduino world. (I realize my own ignorance may be making my progress grossly inefficient…) The main thing is to change the #includes at the beginning of the file. I commented out ALL of the code I could, leaving the declarations (which give “unused” warnings.) I started un-commenting and editing code I needed. When I had something useful, I put a big “#ifdef simulator” before the #includes, and a #else for the includes needed for Arduino. Also, I couldn’t figure out how to change the name from lv_demo_widgets() (VS had a hernia if I did!), so I just conditioned the definition with an “#ifdef simulator”. Finally, I made sure code that interacts with actual I/O is in separate files (e.g., “I2C.cpp” or “Switches.cpp”) and made similarly named files (with artificial returns) in VS land. This allows me to return to VS to optimize the visual interface – great because I can work remotely, then bring it back to Arduino and I only have to comment out “#define simulator 1”. Now I’m very productive and I love it!
Oh. About the examples… As far as I can tell, you just have to pick out the code blocks you need, leaving the outer structure behind. You typically have to study them to at least understand which part you need, and which part is just set-up. After looking at a few, this becomes reasonably obvious.