<@U0F3291QE> on this moment the framework only con...

# tornadofx

[tieskedh]

@edvin on this moment the framework only consists out of onChange with one param.
I like to add onChange with multiple params, but Kotlin has not decided to stick to their own statement about it.
(I'm clearly opinionated about what they should do 😉 ).
See also https://discuss.kotlinlang.org/t/overload-ambiguity-lambda-parametercount

My question is, should we wait and hope that kotlin quickly makes up it's mind,
should we warn users not to use it in combination with onChange and after some iterations add onChange (so we can be consistent in the code)
Or should we add functions with other names, to add these listeners right away?