start/finish trigger direction/ cross S/F multiple times

[leecavturbo]

In a sprint/autocross you have lots of tracks where you cross the start/finish line before the actual finish. How can you set this scenario? A setting to ignore x times S/F is crossed before actual finish?

[Harry]

[Moved to feature request]

There are several approaches to limit triggers from firing. Using a direction is one approach - at least in case the line is crossed in different directions. Next, for AX tracks with separate start and finish lines, e.g. the Go trigger can be passed a second time without an action. LapTimer ignores triggers that make no sense for the current recording state.

I'm certainly aware not everything can be modeled using the above capabilities... My problem is a "counter" approach for triggers will be difficult to understand for many users. Most probably, it would be necessary to invent a completely new approach to define tracks. Some kind of visual modeling? Any ideas are welcome!

- Harry

[leecavturbo]

"Number of times S/F is passed before finish" would be easy to understand. ?
No idea how your software works but if it could be written in like logic (if or and) etc?

[Harry]

Never expect the majority of users being on the same level as you are That's what I learned for product development... If or and are programmer terms, and that's not what most LapTimer users are.

Harry

[leecavturbo]

Haha. Yeah I guess. Cheers for looking/replying