Not sure, but normal url would be protocol://path like http://www.qt.io
: is the protocol splitter delimiter // is annoncing the path follow so based on that, qrc is the protocol, you would need the :// after then the path, since it's a path like a filesystem, it start with / again, making the third one. Not sure why the single qrc:/resource_name is supported, maybe just a side effect as why it work properly or they support at some place the ommission of the path annoncing (which always was a bit useless anyway, but this is my personal opinion on this). Maybe someone can shed some light where the delimiter can be ommit and where it cannot. Jerome [image: bodycad] <https://www.bodycad.com/> Jerome Godbout Software Developer 2035 rue du Haut-Bord, Québec, QC, Canada. G1N 4R7 T: +1 418 527-1388 E: jer...@bodycad.com www.bodycad.com The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message or their agent, or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. Le contenu de ce message et les pièces jointes sont destinés uniquement pour le(s) destinataire(s) et peuvent contenir des informations confidentielles et / ou privilégiées qui peuvent être protégées légalement contre toute divulgation. Si vous n'êtes pas le destinataire de ce message ou son agent, ou si ce message vous a été adressé par erreur, s’il vous plaît avertir immédiatement l'expéditeur par courriel de réponse, puis supprimer ce message et les pièces jointes. Si vous n'êtes pas le destinataire prévu, vous êtes par la présente informé que toute utilisation, diffusion, copie, ou stockage de ce message ou de ses pièces jointes est strictement interdit. On Tue, Nov 29, 2016 at 2:16 PM, Pendleton, Corey < corey.pendle...@garmin.com> wrote: > Hey all, > > The following bug report has been open for a while: > https://bugreports.qt.io/browse/QTBUG-40859 > > The premise is that doing dynamic creation of QML objects using a URL > results in type incompatible errors if you use the form “qrc:/” for your > URL. If you instead use the form “qrc:///” this works just fine. Does > anyone know if this is intentional or a bug? Is there a best practice? > > > > Thanks! > Corey Pendleton > > Sr. Software Engineer > > Office: 913-440-6482 > > > > [image: auto_oem_sig_96dpi] > > > > ------------------------------ > > CONFIDENTIALITY NOTICE: This email and any attachments are for the sole > use of the intended recipient(s) and contain information that may be Garmin > confidential and/or Garmin legally privileged. If you have received this > email in error, please notify the sender by reply email and delete the > message. Any disclosure, copying, distribution or use of this communication > (including attachments) by someone other than the intended recipient is > prohibited. Thank you. > > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest > >
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
