When a custom filter is not available, Dactyl tries loading it from all the custom filter paths, then falls back to the built-in filter path. Import errors on the last step aren't caught & can't be bypassed, but any case of a missing or inaccurate filter falls through to that case.
This gives a misleading error in a lot of cases and interferes with some other things too.
mDuo13
commented
6 years ago
When a custom filter is not available, Dactyl tries loading it from all the custom filter paths, then falls back to the built-in filter path. Import errors on the last step aren't caught & can't be bypassed, but any case of a missing or inaccurate filter falls through to that case.
This gives a misleading error in a lot of cases and interferes with some other things too.