No, I modify with the designer. However I do not think that is relevant.
So it is the Designer that inserts the empty property in the ui file? Is it the default value for that property?
This is relevant as usually trailing and leading whitespaces in xml tags are ignored so if you insert a number of pure spaces into the property, the parser will likely ignore them. If you want, you can use some other (even non-printable) character instead of a space and you should get your desired result. You can also just redefine your property -- if it is the number of spaces that is important, instead of the string property create an integer (or enum) property where you will keep the number. You can even implement the use-number-only-if-text-empty semantics.
I could of course modify everything, but anyhow it worked fine in 4.8 and there is no real explanation what changed in 5.1
regards
You were using an undocumented feature in 4.8. Maybe they changed the behaviour because some other code was broken and was considered more important than your use-case.
I am confused now. I thought the problem was that an empty string was not applied, but now it is about incorrect number of whitespaces?
Cheers,
_
Bookmarks