Closed GliderGeek closed 7 years ago
update: maybe this only applies for taskpoints with sector_orientation == 'next'? if so, it might be to fix the start. should this be enforced more directly? (as sector_orientation can also be next for normal taskpoints)
should actually move all this logic to task. since the handling is specific whether it is aat or race. if taskpoint just contains function inside_sector
this problem is maybe gone?
duplicate, will be solved with #91
seems that it is completed when first fix is inside the sector and the second is out. for racetasks this should be the other way around? (as soon as sector is entered, next tp is selected)