<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body><div>Try to open the map in the right panel first and click on images after that. That's how it works on my system </div><div><br></div><div><br></div><div><br></div><div id="composer_signature"><div style="font-size:85%;color:#575757" dir="auto">Sent from my Samsung Galaxy smartphone.</div></div><div><br></div><div style="font-size:100%;color:#000000"><!-- originalMessage --><div>-------- Original message --------</div><div>From: Martin Bruns <martin@konahina.de> </div><div>Date: 2018-01-22 6:06 AM (GMT-07:00) </div><div>To: digikam-users@kde.org </div><div>Subject: Re: geolocation in AppImage </div><div><br></div></div>Thanks for the information,<br><br>BTW.: I got the same behaviour for digikam 5.6...pre5.9 in case I use<br>the AppImage one. Meaning the geolocation data is only read and<br>displayed when I use the edit geolocation tool, but not when I just mark<br>some images and click on map.<br><br>So anything I can help with further analysing the problem?<br><br>My understanding is that it is somewhere in the MySQL <=> digikam<br>communication.<br><br>M<br><br>Am 20.01.2018 um 17:13 schrieb Maik Qualmann:<br>> The problem is related to this bug report:<br>><br>> https://bugs.kde.org/show_bug.cgi?id=374302<br>><br>> Due to different system and AppImage locale, it comes by MySQL to a wrong <br>> interpretation of the comma / point in double values. I can reproduce it here, <br>> but have no solution at the moment, because it only occurs with the AppImage. <br>> With my native digiKam version I can set any system locale without any <br>> problems.<br>><br>> Maik<br>><br>> Am Samstag, 20. Januar 2018, 16:40:47 CET schrieb Gilles Caulier:<br>>> Hi all,<br>>><br>>> For digiKam 6.0.0 i posted only one entry for GoSC 2018 :<br>>><br>>> https://community.kde.org/GSoC/2018/Ideas#digiKam<br>>><br>>> This one is very important for the future and must be on top level priority.<br>>> We must found a student to work on this project. I will prepare the code in<br>>> BQM previously to be able to host export tool implementations. See my<br>>> previous mail in this room about BQM and export tools for DK 6.0.0...<br>>><br>>> Maik, plan to post a second proposal about this bugzilla entry :<br>>><br>>> https://bugs.kde.org/show_bug.cgi?id=91562<br>>><br>>> The 2 ones are enough complex to manage for me and Maik, If another<br>>> developer want to mentor a student about another topic, please post the<br>>> proposal to the KDE community wiki page.<br>>><br>>> Voila. Have a good week end.<br>>><br>>> Gilles Caulier<br>><br><br></body></html>