xProcess changes default values for Action Parameters
Brought to you by:
acarmichael,
t_shelley
Menu
▾
▴
#92 xProcess changes default values for Action Parameters
When trying to define a default value for an "Action Parameter" of type FLOAT, xProcess changes the default value several times.
If I enter x as a default value, and hit "OK", xProcess will - sometimes - change that value to 10*x. When hitting "Ctrl+S" afterwards, xProcess will again - and always - multiply that value by 10, and change the value to 100*x.
Screenshots attached.
I am using the following version:
Version: Beta 3.6.0.18417
Build id: 3.6.0.18417
Build date: 25-Jan-2012
UPDATE:
xProcess does not show the correct default values when running that action either. (in the updated screenshot, it should be 30)
This probably has to do with an incorrect handling of decimal numbers in parameters on non-english systems. I have noticed a similar effect in the new Task dialog on a German system: if I enter "2,0" this is interpreted/displayed as "2.0"; if I enter "2.0" it is interpreted as "20.0". You can confirm this by adding the line "-Duser.language=en" to xprocess.ini in the root directory of the xProcess installation. "2.0" would then be interpreted correctly and "2,0" would be converted to "20".
It looks like this is a problem not related to language. xProcess is not saving the actions correctly.
I don't know what the reason is but on my German, Windows machine the problem occurs when I run xProcess without any modification and goes away if I start xProcess with -Duser.language=en. I therefore conclude that it is in some way related to language ;-)
I can reproduce the behavior as documented by fgroves. With my system adding the "-Duser.language=en" option to the xProcess.ini fixed the problem as well. So ... what did you, t_shelley, mean, when saying the problem was not related to language?
Anyhow, thanks :-)
Hmmm... when I try and edit the action parameters in xProcess and looking at your screenshots I could see that the default values where shown in the user interface correctly. But if you then reopened the datasource it lost the change. So I'm glad the work around works for you but there seems to be something more serious that happens regardless of language which is why I rasied the priority to 8. I wonder if I should create a new issue for this?