Robin Schmidt

phew - that's a lot to absorb. ...need to read it again... what strikes me a bit odd is that you seem to somehow conflate painting with mouse-handling when you...

so, the main difference to my RSlider::mouseDrag is this: `newDragDistance = e.getDistanceFromDragStartY() - e.getDistanceFromDragStartX();` vs this: `newDragDistance = e.getDistanceFromDragStartX();` hmmm...so it would respond equally to both drag dimensions...but - maybe...

how did you implement the custom ui in fmd? did you subclass all the relevant widget classes? or do you use the `setPainter` mechanism that i added to RSlider for...

hmm..ok. so how do you want that to work? i could imagine to do something like: ```cpp FilmStripSliderPainter : public RSliderPainter { public: setFilmStrip(juce::Image* filmStripToUse, int numSnapshots, bool isVertical); }...

that would assume that one frame is exactly square. but maybe the library should not necessarily assume that - for generality. ...but perhaps the best would be to allow both...

ok - i see. then maybe just the width or height should be passed (because the other one would then be redundant)...we'll see..but yeah `setFilmStrip(juce::Image* filmStripToUse, int frameWidth, int frameHeight);`...

> If you implement this into your library I could delete mine and reference yours. you mean, i could just take this code as is and add it to my...

the "modulatedValue" is actually updated per-sample - you certainly don't want to get per sample-notifications and call repaint per sample. do you want an animated gui that always shows the...

yes, it's certainly a nice to have. actually, it would be best to have both

looking at the inheritance diagram of this: https://juce.com/doc/classAnimatedAppComponent it seems i'm on the right track with juce::Timer. but it's probably wasteful to let each widget be its own timer, so...