Re: [Clip] Re: New calc func sometimes puts commas in 4 digit numbers (and also breaks clips)
- Hi Axel and Joy,
I'm sorry the improvements to ^$Calc are creating problems with your old
Clips. I'm convinced that the new behavior is beneficial to many
(non-vocal) users, especially those with non-US number symbols.
One simple solution to regain the old behavior is to add the
";^%DECIMAL_SYMB%" parameter at the end of ^$Calc in your Clips. Example:
Or use "." if you want to enforce the US decimal symbol:
On 21/08/2012 15:05, Axel Berger wrote:
> "flo.gehrke" wrote:
>> With your parameters '^$Calc(^$GetSelection$+1)$', all integers
>> are grouped like '12,345' in my test.
> This will undoubtedly break a lot of old tried and tested clips. In most
> cases users will no longer remember where and how Calc may be used
> inside them and those breakages will occur erratically and come
> unexpected. Not nice.
> This reminds me of the read-only opening of files after the introduction
> of UTF. In all too many cases I did not notice that my old and reliable
> clip had done nothing and much later was surprised by broken and
> unusable files.
> In cases like these it is actually better not to fake a nonexistent
> backwards compatibility and make the old format illegal. Then you'll get
> obvious errors, not hidden malfunctions.