Bug 402811 - Drag-n-drop disabled in Geolocation editor
Summary: Drag-n-drop disabled in Geolocation editor
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-Generic-GeolocationEdit (show other bugs)
Version: 6.0.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-03 09:07 UTC by Nikolai Malykh
Modified: 2019-01-15 13:43 UTC (History)
2 users (show)

See Also:
Latest Commit: https://commits.kde.org/digikam/83cd159920b89cb1b3dbf1329ae5860877bbe045
Version Fixed In: 6.0.0
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Nikolai Malykh 2019-01-03 09:07:55 UTC 
SUMMARY

Drag-n-drop function does not work in Geolocation editor
STEPS TO REPRODUCE
1. Choose image (any format)
2. Item->Edit Geolocation (Ctrl+Shift+G)
3. Try Drag-and-Drop into map panel

OBSERVED RESULT
Function is disabled.


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Maik Qualmann 2019-01-03 15:16:19 UTC 
You are using Qt-5.12?

Maik
Comment 2 Maik Qualmann 2019-01-03 16:03:26 UTC 
The cause is a change in Qt-5.12.

https://forum.qt.io/topic/97649/bug-in-qt-5-12-drag-n-drop
https://bugreports.qt.io/browse/QTBUG-67155

Maik
Comment 3 Maik Qualmann 2019-01-03 16:09:46 UTC 
Git commit 83cd159920b89cb1b3dbf1329ae5860877bbe045 by Maik Qualmann.
Committed on 03/01/2019 at 16:08.
Pushed by mqualmann into branch 'master'.

fix drag-n-drop with Qt-5.12 in Geolocation editor
FIXED-IN: 6.0.0

M  +2    -1    NEWS
M  +1    -1    core/utilities/geolocation/editor/dialog/geolocationedit.cpp
M  +6    -7    core/utilities/geolocation/geoiface/widgets/mapwidget.cpp

https://commits.kde.org/digikam/83cd159920b89cb1b3dbf1329ae5860877bbe045
Comment 4 Maik Qualmann 2019-01-15 13:43:39 UTC 
*** Bug 403233 has been marked as a duplicate of this bug. ***