ronso0
ronso0
> Unfortunately searching for 98,7 BPM is broken on a German locale. Also using a decimal dot does not fix the issue. This happens also with `main`. Trying to find...
I'll update this PR soonish.
> The matchMode enum is certainly a good idea to make the code more readable, I'll try that. Alrighty, this is much cleaner now. The commit with debug output is...
I think the match lambdas are actually no longer necessary after reafactoring, but it was an interesting exercise. I'm glad it works and CI was happy. Can as well move...
Indeed, UX with/without decimals needs to be improved. However, your observation is not quite correct (it may be that you simply don't have tracks that would be found): `bpm:114`: 113.95...
new debug commit is f306ef1893c2a25bfc43aa30d4caf464a032e1fa
I've added two more cases: HalveDoubleStrict ExactStrict Both are set if the bpm argument has decimals: `bpm:114`: 113.95 - 114.999 `bpm:114.0`: 113.95 - 114.05 Currently already kicks when the only...
And I have to adjust the test to the new behaviour.
> In my test bpm:76 reveals 76.0 76.5 151.0 152.0 153.0 finding 151.0 is surprising, because 151.0/2 is is 75.5 out of the original range. but it matches the expectation...
Done. I'm sorry I had to force-push, I removed the fixup locally. New DEBUG commit is ec9b5570ef