SUMMARY When Google Maps is selected in Map side menu or in Geo Editor, it doesn't zoom like Marble Virtual Globe does. Google Maps zooms with mouse wheel in a browser so in principle this should be able to work. STEPS TO REPRODUCE 1. Ctrl + Shft + G 2. Select Google Maps instead of Marble Virtual Globe 3. Roll mouse wheel over the map. OBSERVED RESULT Map doesn't zoom. EXPECTED RESULT Google Maps to zoom like Marble Virtual Globe. SOFTWARE/OS VERSIONS Windows: 10 64bit. KDE Plasma Version: ? KDE Frameworks Version: 5.49.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION 6.0.0-beta2
I suspect a problem with the used QWebView (WebKit) version. I can confirm the problem for the AppImage and the Windows version. Under my native Linux, the mouse wheel zoom works with both QWebView and of course QWebEngine. I believe I have read that openSUSE QWebView ships with updates and not the original version, which has stopped at Qt-5.5. Maik
Maik, The AppImage and the Windows version of QWebKit (not QWebView witch is the QML interface to native web browser), is the last one available 5.9.1, not the 5.5.0 : https://cgit.kde.org/digikam.git/tree/project/bundles/3rdparty/ext_qtwebkit/CMakeLists.txt#n13 https://github.com/mxe/mxe/blob/master/src/qtwebkit.mk#L11 Gilles
under Mageia6.1, the lib64qt5webkit*-devel are the 5.212 alpha version, so a code not published at stable, later than 5.9.1 : https://github.com/qt/qtwebkit Look the branch 5.212 in git hub and last commit done in january 2018. I know that the maintainer of this component working for Digia left the project after than Qt team decide to promote QtWebEngine instead QtWebkit. Gilles
I have just noticed that with the current Windows bundle the problem no longer exists and the zoom works. Maik
So we can close this file now ? Gilles
No, unfortunately not yet. It works in the Windows version, but not in the AppImage. Maik
Strange, both use QtWebkit framework... I don't yet integrated QWebEngine in AppImage as this need some runtime requirement. Chrome engine use a stand alone broker (service) to dispatch html contents to each Internet tabs. under Windows we will still with QtWebKit for a while, until Google support cross compiling with MinGW. Gilles
(In reply to Maik Qualmann from comment #6) > No, unfortunately not yet. It works in the Windows version, but not in the > AppImage. > > Maik Hmmm. Beta 3 Windows version doesn't work for me.
And i can confirm too that last AppImage that i build yesterday do not work here too. It use Qt 5.9.7. Windows installer build yesterday too, must use Qt 5.12.0 (MXE version if i remember) My native build under Magiea 6 using Qt 5.9.4 work as expected. Gilles
I've tried again the current Windows bundle from 01.02.2019 in a virtual machine and it works. What also stands out is the presentation of the overlays, which is fine under Windows and not in AppImage. The icons for plus and minus or the small figure are moved in the AppImage, but not in Windows. So it seems like Windows uses a corrected version of WebKit. Maik
That i suspected, but the Qt Webkit implementation tarball are typically the same. Perhaps MXE packaging system apply a patch before to compile and install the component. I take a look. Gilles
(In reply to Maik Qualmann from comment #10) > I've tried again the current Windows bundle from 01.02.2019 in a virtual > machine and it works. What also stands out is the presentation of the > overlays, which is fine under Windows and not in AppImage. The icons for > plus and minus or the small figure are moved in the AppImage, but not in > Windows. So it seems like Windows uses a corrected version of WebKit. > > Maik Agreed. In 01-Feb snapshot, Windows now works(thank you) and AppImage doesn't work.
6.0.0 Win64 now doesn't work.
MXE switch to Qt5.11 to Qt5.12. This is certainly the problematic... Gilles Caulier
Created attachment 118258 [details] Map Also very nice to see, if the symbols are not in the center of the white rectangle (see screenshot), also the mouse wheel does not work. Maik
Git commit 65caf571b9002c1c5243e32204bf9280809270a2 by Gilles Caulier. Committed on 09/03/2019 at 16:17. Pushed by cgilles into branch 'master'. switch from QtWebkit 5.9.1 to 5.212 snapshot, the real last version published in january 2018 M +2 -2 project/bundles/3rdparty/ext_qtwebkit/CMakeLists.txt https://commits.kde.org/digikam/65caf571b9002c1c5243e32204bf9280809270a2
Hi, I tried since few week to handle lat QWebkit 5.212 in AppImage, but it's not possible. To compile this code, this require more than 12Gb of RAM. The previous version 5.9.1, compile fine with too enough of memory. So, as MAik patched current code to support QWebEngine without to use extra OpenGL extension which crash violently digiKam here, i started to port the AppImage to QWebEngine... Gilles Caulier
Just as a note, in the Windows version QWebkit works fine again. Maik
yes i known and it's the 5.212... i don't know how MXE can compile QtWebkit without problem... Magic... Gilles
Hardy, I finally solved all my problems with the compilation of AppImage using Qt 5.11.3 + QWebkit 5.212. The problem from this file is solved. New 6.1.0 pre-release AppImage bundle can be found here (64 bits only for the moment) : https://files.kde.org/digikam/ Gilles Caulier
Yes, Windows 64 fixed. Thank you! Will check Appimage tomorrow.
i386 Appimage works also. Thank you.