Hi Chris, thanks for your interest in our problem. The qmldir file just contains the "plugin..." directive, nothing more. The registerTypes(const char* uri) (and therefore the qmlRegistereTypes)is definitely being called when our plugin is in the default directory, because the plugin works fine then (also checked that via qDebug). When it is in our custom path, we are told that the plugin is not even found, so I guess then registerTypes is not called at all (I just checked that too that and the function indeed is not called). So the problem is not the plugin itself, but seems to be some issue with the registering of custom paths. It would be nice, if some windows user could try to reproduce our error. The most of the people here are using Linux, I haven't heard about a similar problem there yet. You could also tell me some more tests I could run.
Thanks again for your help. Greetings Matthias ________________________________ From: [email protected] [mailto:[email protected]] Sent: Donnerstag, 30. August 2012 02:04 To: Wehmer, Matthias; [email protected] Cc: [email protected] Subject: RE: Problems with QmlEngine and importPath Hi, Out of interest, what is the content of your qmldir file? Is your qmlRegisterTypes() function being called at all? If so, does your plugin attempt to install any types into a restricted namespace (eg, QtQuick), or into multiple namespaces? I assume that it isn't, though - are any warnings or errors emitted from QML regarding import type namespace and import path mismatch, or similar? I assume you're on Windows, since you mention that you're using Angle. I don't have a Windows box I can test on at the moment, unfortunately. We did make the QML module import rules more strict, recently (however we also intended to keep current import semantics mostly working, to support legacy modules). Matt (cc'd) should be able to give more information. Cheers, Chris. ________________________________ From: [email protected] [[email protected]] on behalf of ext Wehmer, Matthias [[email protected]] Sent: Wednesday, 29 August 2012 8:37 PM To: [email protected] Subject: [Development] Problems with QmlEngine and importPath Hi everybody, we've tried several other things now and still don't have a clue, what is going on. Does anyone else have any further suggestions or is it indeed a bug that should be reported? Greetings Matthias ---------------------------------- Message: 4 Date: Tue, 28 Aug 2012 09:42:58 +0200 From: "Wehmer, Matthias" <[email protected]> Subject: [Development] Problems with QmlEngine and importPath To: "[email protected]" <[email protected]> Message-ID: <d0c7f8994cdd784c849786cfdbe5a92804443d7...@cdecluexmbx03.corp.draeger.global> Content-Type: text/plain; charset="us-ascii" 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. We are using Qt5 with the angle project and the Qt Creator. That is what we've tried so far: 1. changing the QML_IMPORT_PATH: although this results in syntax highlighting in the Qt Creator, our application still doesn't find the plugins 2. using QmlEngine::addImportPath( dest ) : the path is in the importPathList now, we've checked that, but the plugins can't be found anyway 3. varying the qmldir files: doesn't work either Is this a known problem or is there an error in our application? Thank you in advance for your help. Greetings Matthias (i.e. the syntax highlighting works) in an arbitrary directory as long as the QML_IMPORT_PATH is set. --- 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
