Would be better if 'mir_pointer_unconfined' was the first item in the enum. That way, if we decide to add things like mir_pointer_confined_to_region, the list will continue to look sensible.
33 +typedef enum MirPointerConfinementState 34 +{ 35 + mir_pointer_confined_to_surface, 36 + mir_pointer_unconfined 37 +} MirPointerConfinementState; --------------------------------------------
s/can_set_pointer_confienment/can_set_pointer_confinement
165 +TEST_F(ClientLibrary, can_set_pointer_confienment)
« Back to merge proposal
Would be better if 'mir_pointer_ unconfined' was the first item in the enum. That way, if we decide to add things like mir_pointer_ confined_ to_region, the list will continue to look sensible.
33 +typedef enum MirPointerConfi nementState confined_ to_surface, unconfined nementState; ------- ------- ------- ------- ------- --
34 +{
35 + mir_pointer_
36 + mir_pointer_
37 +} MirPointerConfi
-------
s/can_set_ pointer_ confienment/ can_set_ pointer_ confinement
165 +TEST_F( ClientLibrary, can_set_ pointer_ confienment)