-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Map interaction inconsistencies when items have multi valued location field #2083
Comments
Hi @patrickdalla, thanks. Should we classify this as bug or enhancement? Does it happen with currently supported GPS artifacts or just with the new ALeapp integration? |
I checked the code for ExtraProperties.LOCATIONS references. In GeofileParser, the method set of Metadata is called, with single lat and long passed with ExtraProperties.LOCATIONS, indicating that only one location is added per extracted subitem. But the chat parsers (whatsapp, threema) call the method add of Metadata with ExtraProperties.LOCATIONS of the chat correspondent item, when extractMessages is false to extract individual messages as items. So, there is a possible situation when this issue can occur in past releases. Maybe is better classify it as BUG. |
While implementing a solution for #43, it was found that the maps Aleapp plugin extracted 2 locations per item that represents google maps direction (to and from).
The implementation of map does not expect this, and item selection and highlighting is performing inconsistently.
The text was updated successfully, but these errors were encountered: