Hi Kai, thank you for your suggestions. We also tried that and the QmlImportDatabase told us, that our directory indeed had been added. So it's mainly the same as with the importPathList output.
Greetings Matthias -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Dienstag, 28. August 2012 10:23 To: Wehmer, Matthias; [email protected] Subject: RE: Problems with QmlEngine and importPath > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On > Behalf Of ext Wehmer, Matthias > Sent: Tuesday, August 28, 2012 9:43 AM > To: [email protected] > Subject: [Development] Problems with QmlEngine and importPath > > Hi everybody, > > > > we are currently suffering from the following problem: We fail to change the > default directory for our custom qml plugins, that we have written in C++, and > that we want to import (e.g. via import custom_plugin 1.0). That is the only > directory our QML applications find the plugins is in the default import > directory from the Qt5 directory. What is also strange is that the Qt Creator > recognizes our plugin (i.e. the syntax highlighting works) in an arbitrary > directory as long as the QML_IMPORT_PATH is set. Try to set QML_IMPORT_TRACE in your environment to e.g. 1. If set, your application should print out where exactly it tries to locate stuff ... Kai Koehne --- This communication contains confidential information. If you are not the intended recipient please return this email to the sender and delete it from your records. Diese Nachricht enthaelt vertrauliche Informationen. Sollten Sie nicht der beabsichtigte Empfaenger dieser E-mail sein, senden Sie bitte diese an den Absender zurueck und loeschen Sie die E-mail aus Ihrem System.
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
