Delete Mistyped Chords Option disallows chained chords if any chord by itself is not in dictionary

[Mammal4963]

Describe the bug
Summary:
When the Delete Mistyped Chords Option is enabled - chained chords no longer work as expected.

What happens, and what do you expect to happen instead?
If a chord in a chained chord does not have a standalone chord definition (with the exception of the last chord) then it gets deleted as a mistyped chord and any followup chord entry will not trigger the chained chord output. So for example I can't type Monday using "1 da" because the "1 " does not have a chord definition on it’s own. I expect that because "1 " is a member of a chained chord, it should not be deleted, then if the second chord typed is invalid then everything entered so far should be deleted.

Useful Details

• Which settings do you have selected in the ZipChord settings?
  Delete Mistyped Chords Option: Enabled

• If the output is wrong, what is the sequence of keys pressed, the dictionary entry, and what text appears on the screen?
  dictionary entry: "1 da" = Monday
  dictionary entry: "da" = day
  keys pressed: "1 " then "da"
  output to screen: day

Workaround:
As workaround of course I can make dictionary entries for the 1st chords of chained chord definition for all my chained chords, but this results in a lot of chords that exist that I don't actually want to exist on their own. For example I have this saved "ple zr"=pleasure, but to get it to work I first have to save "ple"=ple, because I don't have a need yet for this chord outside of this chained chord definition.

[psoukie]

That's a good use case I did not think about. Apologies for responding only now. I've been very busy with my day job, but will look into fixing this.