Benjamin Klum

Yes. The goal of the medium-level API is to be 1:1 with the original API, just more safe and with idiomatic Rust. It's the hard part. Building something more convenient...

@Schroedingers-Cat Sorry for the delay. Yes, the drop is the issue. Actually the complete `ReaperSession` gets dropped and the control surface along with it. (Note how this doesn't crash REAPER...

When we move that logic to `reaper-rs`, we should not forget to use `ChangeEvent::is_still_valid()` to only fire it when it's still valid. See method doc for details.

> Hey, I think this is what I intended with #204 ! Sounds like something else to me. This issue is not about a general switch, it's about choosing which...

Did you try adjusting target min/max? That's what one usually uses for and restricting the target range. And it works for "Make relative" as well.

Yes, then I guess this FR here could be useful to you. It would allow you to conditionally switch between to "Make relative" mappings with different step sizes.

When implementing this, "Make relative" should also be improved so that repeated arrival of 1.0 increases and repeated arrival of 0.0 decreases. This makes it possible to easily deal with...

Looks like this can be solved now via `include_str!`: https://blog.rust-lang.org/2021/07/29/Rust-1.54.0.html

> A few questions came up, maybe you could answer some of them? :) I'll try as far as I can. I just sometimes have to refer to the REAPER...

> Thanks, everything is working fine now. Good to hear :) > (Yeah, the problem was that I had dropped the session.) > And `count_tracks` indeed works when Reaper is...