Interesting. This sounds similar – I also need to maintain a particular data model.
I also looked into @dave96’s constrainer approach to maintain values within a certain range, but then I discovered that it actually only constrains the “cached value” that the class in question sees, it doesn’t actually enforce the constraint on the actual ValueTree property that the rest of the world sees. So it looks like I need to come up with my own solution for that as well.
One problem I see is that, as @alibarker noted above, the order in which the different ValueTree::Listeners are called is not guaranteed, so I can either have individual properties listening to the tree, or the outer class listening to the tree, but never mix and match both (which was the mistake I did in the original post).
This is indeed not easy to figure out 