mirror of
https://github.com/keymanapp/keyman.git
synced 2026-10-20 12:57:49 +00:00
4f1435c274
When SearchQuotientCluster nodes are split, there is no guarantee that the split will be perfectly clean for all paths leading into the cluster. Even if so, there's also no guarantee that it will be placed the same way for all such paths. Suppose the following cases: - a, bc, d, e - a, b, c, de Splitting at index 3 may result in a clean split both ways, but the first sequence splits after the second input, while the second sequence splits after the third. These cannot be clustered together due to representing different (diverging) intervals of the user's keystroke-input sequence. Splitting at index 4 has its own version of this problem: the first sequence splits cleanly after 3 inputs, while the second splits in the middle of the 4th input. Again, the represented input intervals diverge, requiring different representations for the split results. Build-bot: skip build:web Test-bot: skip |
||
|---|---|---|
| .. | ||
| attachment | ||
| common/web-utils | ||
| dom-utils | ||
| element-wrappers | ||
| events | ||
| interfaces | ||
| js-processor | ||
| keyboard | ||
| keyboard-storage | ||
| main | ||
| osk | ||
| predictive-text | ||
| sentry-manager | ||