I think this mechanism is a bit weird (!)
 * it only seems to apply to the splittable-int cases (? not quite clear about this?)
 * it relies on the setter function saving the "transformed" form, instead of the 'value' passed
 * it also relies on the setter accepting *either* the required-form or the plain int version of the property