#16 Photos with no timestamp abort the Correlate function

[Micha]

If one (or more) photos are added which don't have a timestamp, the Correlate function aborts with a Null-pointer exception.

Exception in thread "Thread-17" java.lang.NullPointerException
at tim.prune.correlate.Correlator.getPointPairForMedia(Unknown Source)
at tim.prune.correlate.PhotoCorrelator.createPreview(Unknown Source)
at tim.prune.correlate.Correlator.createPreview(Unknown Source)
at tim.prune.correlate.OptionsChangedListener.run(Unknown Source)
at java.lang.Thread.run(Thread.java:662)

A workaround (ie, not a fix, just a hack) is to just skip media files with NULL timestamps (which 'works for me' for now); see the attached diff file.

I can think of three approaches to fix this:
1) Ignore NULL timestamped files, as I have done.
2) Handle NULL timestamps properly everywhere
3) Display an error message which includes the offending file(s) so the user can remove them from the list

[Micha]

Workaround patch

[activityworkshop]

Oops, you're right, I can confirm this on 13.4 and also on the forthcoming 14. It appears to assume that the photo has a timestamp, because even if it couldn't find one in the exif information, it should always be able to find one in the properties of the file...

Except of course that now photos can be loaded not only from file, but also from inside kmz files or from http streams, so those ones don't have timestamps. (Such photos always have points, too, which is why I don't often try to correlate them!)

I like your idea of just ignoring those photos, and just attempt to correlate the ones which do have timestamps. I don't think an error message is necessary. I'll get this fixed for v14.

[activityworkshop]

Please test this again with v14 (available from the development page)