Lua:Class:CheckBox

Currently in AT-SPI there is a discrepancy. The user has a sligne gesture to change to the opposite state depending on the current state but the actions define in specific end states (check or unckeck). Is there a good reason for this? If the AT wants to give the user the same experience as the direct user then it must look at the current state and use the correct action to give a similar toggle effect.Following that logic you should expose both Check and UnCheck in the indeterminate state and let the AT do all the work. Yuk how did we get here?If there is a good use case for an action that ends in an unknown state as determined by current state and application logic then Toggle might do as you suggest. To my mind toggle indicates change to the other state of 2 states so isn't right for tri state logic where Cycle, Change, Alter. NextState, might be better suitedHey how about