You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 10, 2022. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: