@Maluna34 maybe the qrc file mechanism is not the best approach for what you intend to use; however you only know your actual requirements.
From documentation about Qt resource system:
The Qt resource system is a platform-independent mechanism for storing binary files in the application's executable. This is useful if your application always needs a certain set of files (icons, translation files, etc.) and you don't want to run the risk of losing the files.
so a music file for a whole opera concert is not a suitable candidate for being stored in the qrc file as it ends up into your executable.
Given that said, you could get the file from the resource and save it somewhere to disk so the external tool can access it.
which then causes a lookup of Navigation.qml (and yeah, I did still have to give it an alias in the .qrc file, for some reason...)
Not sure why I had to do this from my reading of the documentation, but it's at least a workable solution.
Seems like QML only resolves components only with .qml extension.
Your solution wokrs because import "./components" as Components imports the whole folder 'navigation'. Then you use the component Components.Navigation, which then is loaded by the engine as Navigation.qml.
On that link is the print screen of my qt project http://i68.tinypic.com/mm6d6u.png
Is a few images, but if in 2 Ui's i add the images with the resource directly, and in the third widget i add manually, will be a few wrong to me." Why she's do that in this way here and another way there?"
@alex_malyu I re-read and you are right. I was sure that only the main expansion file was downloaded and that the patch file download had to be initiated by the app, but this is not the case. At least for now a work around is using two files, but I might get the same problem when the app expands.
I am using Windows 7 64-bit and have tried MinGW 4.9.2 compiler on Qt 5.5, MinGW 4.9 on Qt 5.4.2 and MinGW 4.8 on 5.3. I also tried MSVC2012 on Qt 5.5.
I will try post a bug report and see if someone can reproduce the same.