[John]

Installed Felgo on a new Windows 10 workstation.  It has a working Qt commercial license installed and working.

The AppPlayground project opens with the Welcome tutorial.

First, line 1 import Felgo 3.0 says QML module not found (Felgo)

Second, no kit was attached.  Followed link and selected the only available, Desktop Qt 5.15.2 MinGW 32-bit

Now says:

The currently selected kit “Replacement for “Desktop Qt 5.15.2 MinGW 32-bit”” does not have a valid Qt

I suspect something needs set in a path or directory.  Any thoughts?

Also have a display issue which I will note in a second topic.

[AlexFelgo Team]

Hi John,

did you use the installer from https://felgo.com/download or a version from the Qt Marketplace?

Are you also using Qt 5.15.2 with your commercial installation? The “Replacement for …” kit name is created by some Qt Creator mechanic mentioned here, that might have interfered during the Felgo installation. Felgo installs an own default kit and no manual configuration is needed usually.

Since you mentioned the playground project opening, I assume you have opened the Qt Creator from the Felgo installation folder? Please double check that there is no other kit available in the project settings. You can also send us screenshots of your kit and compiler settings to support@felgo.com .

I would also suggest to do one more fresh install of Felgo, to rule our any potential issue during installation itself.

Best,
Alex

[AlexFelgo Team]

I also got the info that removing the replacement kits should be safe and can help. Anyway there should be a kit without the “replacement” available as well after the Felgo installation, that should work properly. If that is not the case, please try reinstallation once and if there are issues again please send us the screenshots as mentioned above.

Best,
Alex

[John]

Alex,

Removing the replacement kid did indeed resolve it.  Interestingly, even when starting a new project and the only kit option available was not the replacement, it switched to the replacement anyway.  Removing the replacement kit allowed reselecting the original kit which then worked as expected.  Thanks for your assistance.  Part of the difficulty with this was due to a second issue which I will create as a second topic in case anyone else is experiencing it.

[AlexFelgo Team]

Hi John,

thanks a lot for that report. This is indeed an inconvenient behavior caused by a very recent feature of Qt Creator. We’re looking into improving the compatibility with a second Qt installation on the system.

Best,
Alex