O.k., Danke. Der Darstellungsfehler passiert bei speziellen Situationen. Ich habe das jetzt robuster gestaltet - sollte ab der nächsten Version nicht mehr auftreten.

The data attached does not contain engine data. So the MX connection dropped for some reason or the MX has been used by another app in background.

Yes, you can log data after enabling "Manual Timing" in Settings. This will add "Start" and "Stop" buttons to Timer View.

Provided you make sure (in your track definition) LapTimer will not pick up a T1 trigger when started by T2 (and vice versa), this scenario is fine. So from I see in the sketch - you can ignore the warning. The conflict detection is pretty dump. It just creates a rectangular area from all POIs belon...

Wait - this looks like the top right sector indicator ("1" in my picture) has been shifted over the center part of the large display covering the ":4" part. Can you reproduce this? I'd be interested to know about the system situation the screen shot has been taken, how many secto...

That’s a display error from iOS… Actually these are two text fields showing a large and a small string… LapTimer tells iOS to display “2:42” with a large font and “.16” using a small font. It should look like …

This looks like some low level corruption for the font used.

Harry

By pressing Staged, you confirm you are staged for a standing start. This means you stand still and wait for signal to accelerate. There are two types of Autocross starts - either this staged / standing start approach where timing starts when you start accelerating, or a regular start by passing a c...

No problem but both are empty. This means there is something wrong with the database. This can be the reason for recording interruptions as well as for the error dialog posted. Please start with chalking your Lap List. Do you see all laps duplicated? This is usually the result from a double restore ...

Hello, LapTimer for Android and iOS utilize the exactly same code for trigger detection and data handling, it is just the user interface that is re-implemented by platform. So i case two devices behave different although they use the same settings, it is some GPS data issue or OS setting. Please rec...

Thanks for the video. You are right, dragging POIs around is not working well currently. It has always been difficult to implement because a drag operation can be either one to select a different map location (i.e. move the visible area around) or dragging a POI. One of the recent iOS version change...