Value object weirdness

Hey Jules -

I’ve been sitting on this one for a while, and am sure I am doing something wrong … but haven’t been able to get past it.

I know Value objects are totally thread-safe, but I seem to get a strange crash occurring once in a while with Value::setValue(). I’ve attached the call stack, and you’ll notice that the MM thread is doing an internalRepaint on a component, which has responded to a ValueChanged() originating at (I suspect) the same Value object.

Any clue what’s going on here? I must be doing something wrong.

Value objects are totally NOT thread safe!

Ha! Well alright then, I’ll throw a lock in there, thanks.