Anyways, I changed the applications name to a custom one (not ModelViewDelegate), and thus I should have changed that import to import {customAppName}, doing it like that resolves the build errors.
Still the "Property 'sendRequest' of object Requester is not a function" run-time error is not resolved, but that is for another post.

👍

I am using Qt Creator 20.0.1, that QML_IMPORT_PATH is set because when i choose 6.8 and up (instead of 6.10 and up), there is a checkbox for that QML_IMPORT_PATH which is selected automatically.

My bad, I misdiagnosed the message. That particular appeared because the QML Language Server is disabled (see https://doc.qt.io/qtcreator/creator-how-to-use-qml-language-server.html )

The checkbox is for QT_QML_GENERATE_QMLLS_INI (deprecated since Qt 6.10), rather than QML_IMPORT_PATH (deprecated since Qt 6.5, or some might say Qt 6.2).

@JKSH It is this one https://academy.qt.io/content-details/337375027/2

The example code for that tutorial is at https://github.com/qt-learning/Model-View-Delegate

@DSpUz said in import ModelViewDelegate fails:

How do I import it if its not on my system by default for some reason?

That project's QML files can use import ModelViewDelegate because there is a project-specific QML module (see https://github.com/qt-learning/Model-View-Delegate/blob/main/00_InitialProject/CMakeLists.txt#L28-L29 ):

qt_add_qml_module(appModelViewDelegate
    URI ModelViewDelegate
    ...
)

One more thing: What version of Qt Creator are you using? Your screenshot shows that it's recommending that you set QML_IMPORT_PATH, but that was deprecated long ago. If Qt Creator is too old, it won't know how to find your project-specific module. (If this is the case, you'll see invalid errors/warnings in your code editor, but your project can still run fine)

the submodule is not mine but from the
QML basics tutorial

I'm not familiar with this tutorial. Can you please share a link to it?