WGTicon:
I am guessing it's easier to always have it rather than add more logic to wait. I agree, it's not ideal but imo not a deal breaker. I want us to fix other things first before checking on this :)
-wgticon
Hey Icon ... no offense meant but I do know a bit about programming. How hard is the code statement ...
NoMulligan = True
or ...
FirstSwing = True
at the end of the 9th hole. This is the only hole where it shows up on the first swing ... hole #10 when playing an 18 hole game.
Since there are "Play 9" and "Play 18", it seems like there's a boolean test field being used to trigger the "NoMulligan" and "FirstSwing". The programmers just oopsed this one.
It is a bug ... and a really easy bug to fix. You're trapping this on every other 1st swing except #10 of an 18 hole game.
BTW, if you click this on the first swing, the game locks up! I guess it's looking for a non-existent swing.
Please do what you do to let the "engineers" know!