Because converters are run when setting a widget value, this can trigger registration with the object service which then makes the converted value available on subsequent runs. If the pre- and post- conversion objects have a different toString representation then they will appear different.

This branch resolves the issue by aggressively converting, but that seemed overly aggressive and likely to have unintended consequences.