Ability to "turn off" a track without purging it
Ability to "turn off" a track without purging it
I don't know that this would have a lot of track use, however for "tracks" created on streets (drive to work, etc) it would be useful. For my drive to and from work, I take different routes depending on time of day. Currently I have start triggers part way along each of the separate routes so there is no overlap. However, being able to simple turn a route off would be great because I could record a longer section of each route.
Re: Ability to
Hi,
LapTimer has a very primitive conflict check: it simply checks if there is a non-empty intersection between the bounding *rectangle* of track A and B. So in case you know there is no conflict in reality, simply ignore the warning.
- Harry
LapTimer has a very primitive conflict check: it simply checks if there is a non-empty intersection between the bounding *rectangle* of track A and B. So in case you know there is no conflict in reality, simply ignore the warning.
- Harry
Re: Ability to "turn off" a track without purging it
I have been ignoring them, but this request was specifically to address issues with multiple stop and start triggers being used to track multiple different routes home. As I noted, it probably is useless for most people on the track (except possibly when a track has multiple configurations possible).
Re: Ability to
Here a related topic: https://www.facebook.com/photo.php?fbid ... =1&theater
There have been several discussions on track activation / inactivation already. My résumé so far is a mechanism like this will generate at least as many issues and disadvantages as the current mechanism does.
- Harry
There have been several discussions on track activation / inactivation already. My résumé so far is a mechanism like this will generate at least as many issues and disadvantages as the current mechanism does.
- Harry
Re: Ability to "turn off" a track without purging it
I had seen that image when searching earlier, however for some reason I chose not to follow the instructions. 
I will modify my tracks now that I understand that both the go and stop triggers affect which course is being recorded.
If you don't think it's a useful / feasible idea, then please don't feel like I'm demanding it or anything like that. I was just trying to spur conversation and debate ideas for creative purposes.
I will modify my tracks now that I understand that both the go and stop triggers affect which course is being recorded.If you don't think it's a useful / feasible idea, then please don't feel like I'm demanding it or anything like that. I was just trying to spur conversation and debate ideas for creative purposes.
Re: Ability to
No problem. I appreciate any suggestion here on the forum. I'm aware that custom track definitions suffer a bit from the current design. Besides the effort one has to take to add activation / inactivation, this pattern would introduce another concept to LapTimer's already existing complexity, and there will be many users accidentally in-activiating track sets they actually wanted to use. This in turn would require additional testing for error situations and so on.
To backup your custom track definitions, you can "Certify" the track set and send it to yourself (instead of me), which in turn allows you to recreate the track set from mail at any time.
- Harry
To backup your custom track definitions, you can "Certify" the track set and send it to yourself (instead of me), which in turn allows you to recreate the track set from mail at any time.
- Harry