Bug: delete_chordmap(chord: Chord) weirdness

[rayluo]

Hi there, so I start fiddling with my charachorder device and my little project again. And I ran into some weirdness of the delete_chordmap(chord: Chord).

1. It seems that, the chord - which is actually a tuple - shall be in a consistent order for it to match successfully. That makes sense, but the docs shall mention that, and ideally the Chord class shall auto sort the input so that it will always have a consistent order. For example, chord "the" shall be sorted as "eht".
2. After I presort the chord, the calls of delete_choadmap(...) still returns False, indicating an error. Indeed, the debug log shows an error code 2, HOWEVER the deletion was actually successful.

DEBUG:charachorder.device:[CharaChorderLite M0 (/dev/ttyACM0)]: Executing 'CML C3 00190610000000000000000000000000 646164'...
DEBUG:charachorder.device:[CharaChorderLite M0 (/dev/ttyACM0)]: Received 'CML C3 00190610000000000000000000000000 646164 0'
...
DEBUG:charachorder.device:[CharaChorderLite M0 (/dev/ttyACM0)]: Executing 'CML C4 00190610000000000000000000000000'...
DEBUG:charachorder.device:[CharaChorderLite M0 (/dev/ttyACM0)]: Received 'CML C4 00190610000000000000000000000000 2'