Yes, the iNaturalist login page can no longer be used with the QWebKit browser engine that we use in the Windows version. At the moment we cannot use a newer browser engine in the cross -compiled version.
There is a nightly digiKam bundle created with the Microsoft MSVC compiler. This uses the modern QWebEngine (chromium). Restrictions are currently not a MySQL and HEIF support.

https://binary-factory.kde.org/view/Windows%2064-bit/job/Digikam_Nightly_win64/

Maik

Compared to the upload interface of the iNaturalist website, this add‐on is unfortunately way behind.

It should allow to select images for several observations. Just one, like we have now, would be acceptable if the the workflow was seamless.

The initial dialogue box asks to confirm the account that you use (for each observation, as said earlier!). This is unnecessary for the vast majority users, except for the very few that use several accounts. Either remove this confirmation or have a check box to use one account only or, if possible, select your account (and remember the last one used) rather on the main upload interface, especially that it’s already reminded there.

Now, if you have set an account, to make things worse, you have to click with the mouse on OK to confirm the account. If you hit the Enter key (which would be much faster), you are caught in a trap: add another account. Needless. Even if there is the initial dialogue box, the Enter key should be the default so that you quickly move to the upload window. At the very least there should be a shortcut key.

If you do something else (click the Close button or even click on the × in the window bar to close it), it asks you to add an account. Why?

Then on the main interface, there is enough space. Let options visible, like the possibility to add a comment, don’t hide them. Also, the cursor should be already on the required field; that is the species name.

The Start updoad button is so slow (sometimes almost one minute, even with a good connection, whereas the direct upload on the iNaturalist website is instantaneous) and you can’t do anything during that time. Why so long and why are we blocked? After a while it finished uploading and the Close button silently appears. Why not just close the window since you can’t do anything else anyway, that is combine Send and Close? It would be easier to spot when it finished.

For my test here, the upload is very fast on my computer (Kubuntu 22.04). My digiKam is a compiled version, not a sand-boxed bundle as Flatpak or Snap where external access a voluntary limited by design (We are not responsible of this at all). There are settings in the OS to open the doors for this kind of bundles, but it's to much complicated as users expect to see the application working as well without tuning. This is why we don't supports officially Snap and Flatpak.

I recommend to try the AppImage version of digiKam. This kind of bundle that we provide are not limited.

Gilles Caulier

Thanks Gilles for the explanation. It might be useful for Linux users.
In my case, the upload delay is with Windows.
And I suppose that all the other quirks I described are OS‐independent.

Regarding

> The initial dialogue box asks to confirm the account that you use (for each observation, as said earlier!).

there is no need to confirm the account for each observation. Confirm the account for the first observation. Then leave the iNat export window open and drag your photos for subsequent observations into that window.

While an observation is still uploading you can already drag photos for the next observation into the export window and add your identification and comments.

Close the export window when all your observations have been uploaded.

Joerg

Indeed, that helps to do things faster. This is totally unintuitive because the export window takes the front of the screen and if you click in the main digiKam window, you lose the upload window. At least you can do something while it’s doing something…
Maybe the upload window should invite you to drag and drop other images in the mean time, otherwise most users won’t know. But it’s still one observation at a time.

But honestly, after trying both the digiKam export and the iNaturalist web interface today, the latter is so simple and efficient, but I can’t say it about the former.

@Patrick,

This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:

https://files.kde.org/digikam/

This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110.

Thanks in advance

Gilles Caulier

@Patrick,

The new digiKam 8.2.0 pre-release Windows installer is online. This one is
built with VCPKG + MSVC toolchain and Qt6. It's a native version compiled under
Windows 10. File is here:

https://files.kde.org/digikam/

Please test and report to see if problem remain.

Best regards

Gilles Caulier

Hi all and happy new year.

What's about this file using 8.3.0 pre-release bundle available at usual place :

https://files.kde.org/digikam/

Problem still reproducible ?

Thansk in advance

Gilles Caulier

For now, I count on Patrick to check.
I haven’t migrated to Windows 10 yet, so I can’t verify.

In all cases, if you migrate to Win10, uses digiKAm 8.3.0, not 8.2.0. We have fixed plenty of bugs for Windows in 8.3.0.

Gilles Caulier