The comma point thingy is because of your system’s culture. You probably use a system which is from a culture that usually uses a comma for decimals and not a point as they do in USA.
Using commas will result in the array editor assuming you want to use multiple values to increase in a row like 1,2,3 will result in an increase by 1 for the first entry, 2 for the second and so on and will begin at 1 again after 3.
Unfortunatelly there isn’t really a good workaround for this unless you want to reinstall your system in English language or find a way to modify your system language sufficient enough to change it’s culture.
@Devs: This is a really nasty issue for all German users and other languages where commas are used instead of points. It’s impossible to use this feature for us since the system does not recognize a point as valid seperation symbol and therefore will convert into an integer value instead of a float. Since reproducing this issue will be hard on us systems, I’ve had a look at the code of the array editor and found the following line causing the problem:
numArray[index] = float.Parse(strArray[index]);
From the buttonIncSeries_Click event in the array editor. To resolve this problem, simply add the following to all parts where you use float.Parse:
numArray[index] = float.Parse(strArray[index], Culture.InvariantCulture);
or alternatively
numArray[index] = float.Parse(strArray[index], new Culture("en-US");
as this will ensure that the value will get converted correctly when using a point as seperation symbol. The only problem is that it will convert the output value to use a comma with the right value on German / other comma culture systems so you’ll have to replace the comma by a point in the output by hand to prevent errors when using a second operation.
Also this issue will occur everywhere where float values are used. People probably can use commas instead and make it work unless commas have another special meaning like in the increase series part but it’s getting mixed up and might be confusing.
@ASYLUM101 this is the exactly same issue you reported to me when I was working on Grim Manager value editor just that I didn’t know about culture differences causing this problem by then. It always worked at my system due to it using commas instead of points and therefore gave you trouble.