Thanks for a quick response. Just to be clear - it isn't just the PositivePattern that is causing a problem, the same goes for NegativePattern.
When trying your workaround I found some more bugs regarding this issue. Your workaround with updateDisplayValue() works fine for the pattern "n tons", but for a pattern of, for example "tons n" it renders an empty string ("").
So, to summarise my found issues (for both positive and negative patterns):
- The server side renders the value for every occurence of 'n'.
- The client side renders the value for the first n, which makes it impossible to have a pattern where the first n should be considered a literal.
- Calling updateDisplayValue() on ClientEvents-OnLoad renders empty text when the first character isn't an 'n'.
- Calling updateDispalyValue() on ClientEvents-OnLoad with a pattern of "nn" and value 123 renders "123 123n" which is so strange that I can't even find a reason. :-)
I have no problems using the workaround since I want to display "n tons", but I just wanted to make sure that you got all the bugs in one fix. :-)