Caching mechanisms on GPX layers

[Niklas B]

(maybe this time..?)

Hi,

I'm currently implementing an option to cut overlapping GPX tracks when
merging them into one layer (followup of #16681
 "*allow multiple tracks to be
processed and prioritized (from different sources, e.g. GPS + phone +
Google Timeline)*", but when merging layers because this is not
specifically related to geotagging / geoimage layers).

Everything works fine, but the resulting GPX layer is not displayed
correctly: Some lines are displayed between tracks that are not connected
anymore (because another track was on top of it, so the underlying track
needed to be split) and also some weird lines connecting points that were
never connected appear - haven't figured them out yet.

Before I debug that any further: What caching mechanisms are there in
place, what do I have to reset? I'm already calling invalidate() (in
GpxData, which calls the appropriate listeners) and tried removing the
cached "dir" values from all of the waypoints, but it didn't help.
The layer will however be displayed perfectly fine if it's converted to a
data layer (and back) or saved as GPX and reloaded.

Any ideas on what might be the reason for that?

Thanks,
Niklas (Bjoeni)

Another try: Caching mechanisms on GPX layers

[Niklas Burchard]

Caching mechanisms on GPX layers

[Niklas Burchard]

Re: frozen editor while panning or zooming of the map

[Stephan Knauss]

On 14.09.2018 09:12, Dirk Stöcker wrote:

Hello Stephan,


Shall I create a ticket with the details up to now to better track it?


Yes. Please create a ticket and copy all relevant details there. 

created https://josm.openstreetmap.de/ticket/16734

Discussions in the mailinglist tend to be forgotten, the JOSM wiki is 
our main communication channel (as you can easily see when you look at 
the timeline :-).
I hoped the mailing list being a bit more interactive so to easier track 
down the issue.


Please let me know if any further details/reproduction are needed.

Thanks,

Stephan