When running qmllive with a given command-line importpath, but having another import path set in preferences, qmllive will ignore the command-line one when reloading after files change.
When calling qmllive as such:
$ cd project-a/$ qmllivebench -importpath ./imports ./ Main.qml
And having set some other import path in preferences of qmllive (say, project-b/imports), then qmllive complains when reloading after some file in project-a changes if one tries to use components that are not in project-b/imports.
I'm not sure about what would be most reasonable, but I think command-line arguments should take precedence over the stuff set in preferences.
When running qmllive with a given command-line importpath, but having another import path set in preferences, qmllive will ignore the command-line one when reloading after files change.
When calling qmllive as such:
$ cd project-a/
$ qmllivebench -importpath ./imports ./ Main.qml
And having set some other import path in preferences of qmllive (say,project-b/imports
), then qmllive complains when reloading after some file inproject-a
changes if one tries to use components that are not inproject-b/imports
.I'm not sure about what would be most reasonable, but I think command-line arguments should take precedence over the stuff set in preferences.