Thanks! after reinstallation it really works

Use QStandardPaths and store settings using QSettings. It's simple and the standard way of doing things.

@wilke18 please see here: http://doc.qt.io/qtcreator/creator-project-wizards.html

Ignoring the Qt specific aspects of integrating a 3rd party library for just a moment, I would like to ask - are you implicitly or explicitly linking these DLLs into your application? Implicitly linking means (in case you don't know) means your code links with a *.lib that makes yours application need the DLL in order to run but also means you don't have to locate the functions you want to use in the DLL when your code runs. This is most likely the way you plan to use these DLLs. Explicitly linking means you don't do anything with the DLL until your application starts up - at that point your application code manually loads the DLL into its process space and your application code looks up the actual functions you want to use in the DLL. This is a very flexible way to use DLLs but you're probably not doing this.

Too bad. May be I'll try to make a Qt Model for it my self.

I was having this same problem, turns out I was restarting too soon. The file transfer was so slow that took over a minute to transfer a 2Mb file. I still don't have a good solution, I am using system("cp file1 file2") for Linux as a workaround, but don't have any suggestions for a portable solution.

Hi @neovius and Welcome, When i change the backlight slider, the signal is emitted, and received. but i still get the warning when starting the application : That is because you are creating QML component before setting the context property and thus naturally it wont be able to access that method at very first time. http://doc.qt.io/qt-5/qtqml-cppintegration-exposecppattributes.html#exposing-properties http://doc.qt.io/qt-5/qtqml-cppintegration-exposecppattributes.html#exposing-methods-including-qt-slots

Thank you Anant, I will be deploying both to Linux and Windows and so require a solution for both, however they don't necessarily have to be the same solution. Many thanks

Writing a small compiler ?

For Android you can use the Assets file system

@Varius said: thread = new QThread(this); console->moveToThread(thread); IIRC, these lines are doing more than you think they do. thread's parent is your object, then you move your MyObject instance to thread, so all objects who are child of your MyObject instance are moved the thread. So thread will be moved to itself. All in all, you should rather have thread in your main as a stack object

You can't load Qt dlls when you want to simply because they are linked to your program and need to be resolved at startup. That's just how it works. If you were to load Qt dlls when you wanted (e.g. using QLibrary) you would have to also manually resolve addresses of all functions and classes. It's possible but just impractical at this scale. But here are two ideas what you could do: One way would be to split the app in two. First one would be the loader (the dialog) and it would use QProcess to start the main app when it finishes its work. Handy for updating the main app too as it's a separate file. The other idea would be to make your main app a shared library and load it dynamically with QLibrary at the right time. Same benefit as above except an exe and a library instead of two exes.