Robin Schmidt
Robin Schmidt
how/why does that even compile? :-O
ahh..ohh. ok, i see. so there's an implicit conversion from the "myparams" object to double due to having defined a double() operator? uuuuhhh.....that's....well.....let's say....non-obvious. i might say confusing. i'm even...
but anyway, i think, i could write a smoother class for you based on EngineersFilter which has the same interface as the ExponentialSmoother (plus some additional setOrder function, maybe also...
ok - i'll check that tomorrow
yes, i think so. it's not something i use a lot, though.
ok - i think, i know what the culprit is. you do things like: ```cpp paramStrIds = { &(FXMode = myparams(i++, BUTTON, "FXMode", 0.0, 1.0, 0.0)), &(Pause = myparams(i++, BUTTON,...
i could manually implement a more suitable assignment operator in EngineersFilter - but actually, i do not intend my dsp objects to be copyable/assignable like variables. things like `EngineersFilter filter2...
wait...no... i think, using a pointer still wouldn't work
> I got something working i think, the cleanest solution woud be to get rid of using the = operator here: `FXMode = myparams(i++, BUTTON, "FXMode", 0.0, 1.0, 0.0)` by...
i have now declared the copy-constructor and assignment operator as "deleted" in rsEngineersFilter, so now the compiler will balk on any attempt to copy rsEngineersFilter objects. i should really use...