Found the button in the client window, in Actions -> Clear project cache and reload.
I found out that Felgo creates cache at: C:\Users\<username>\AppData\Roaming\Felgo Live Client\<projectname>.
The said button cleans all folders at that location.
However, this does not help with the issue. Therefore, a feature suggestion to Felgo: Monitor the actual structure and settings of the user as per the qml locations, and reproduce that structure in the cache and build folders.
Manual solutions to the issue:
Create your wanted folder structure in the project folder
Change in .pro file: qmlFolder.source = <your wanted path>
Change in main.cpp: felgo.setMainQmlFileName(QStringLiteral(<location and name of your main qml file, relative to proj path>));
To use the live client with custom folder structure: Copy your custom structuring to the cache location mentioned above
To debug and dev normally by running with Qt Creator, you also need to replicate custom structuring at the build folder
At deployment, things should be changed to use .qrc, I believe, and that will mean other modifications.
Just wanted to add that it was not actually so easy, the above does not completely work. Copying things doesn’t work, symbolic links might work. However, with custom structures, you’ll lose the straight updateability upon pressing Ctrl-S to the live client window — you need to activate the window and press Ctrl-R. Not sure if applies to the custom live client build, and don’t have time to investigate further. The default foldering is recommended for now, which is a bit disappointing.
Also, perhaps no need to do anything at the build folder, just rebuild.
Anyway, App also links FelgoLive in the CMakeLists.txt and starts the live client at the end:
Upon connecting I get
MyProject/src/com/my/org/App/main.qml: No such file or directory
Your 6.4 example projects work just fine. I don’t want to mess with my existing project too much. I tried copying it into the cache folder but it didn’t work either and even that was a headache given my Core module lives outside the App directory.
Ideally, I don’t need to make any changes to my CMakeLists besides linking to your library.
In case there’s anything else I can provide to help debug this issue please let me know.
the Start button in the Live Server will always start the default Live Client shipped with the SDK (thus the import fails). If you are using the Live Client Module in your own app, you will always have to start your own app and connect it to the Live Server.
I have forwarded the stack traces to the tech team, thank you for your effort. If we can get any insights from them, I’ll let you know. You could disable “Hot Reload” in the Live Server and only use “Live Reload” (so without preserving the application state) at least, to still speed up development by avoiding build/run steps.
Want to find out if Felgo is a good fit for your company?
As part of the free Business evaluation, we offer a free welcome call for companies, to talk about your requirements, and how the Felgo SDK & Services can help you. Just sign up and schedule your call.
Sign up now to start your free Business evaluation: