Global.alert("base: " + base + ", upfront: " + upfront + ", both: " + (base + upfront));
The code above outputs something like:
base: 15000, upfront: 36, both: 1500036
Why is it joining the two numbers instead of adding them up?
I eventually want to set the value of another field to this amount using this:
mainPanel.feesPanel.initialLoanAmount.setValue(Ext.util.Format.number((base + upfront), '$0,000.00'));
And when I try that, it turns the number into the millions instead of 15,036.00. Why?
This might happen because they are strings. Try parsing them:
Global.alert( "base: " + base + ", upfront: " + upfront + ", both: " + (parseInt(base) + parseInt(upfront)) );
If those numbers are decimal you will need the
parseFloat method instead.
1 +1 == 2 "1"+1 == "11" "1"*1 + 1 == 2
Ways to turn a string into a number:
And here are some of the consequences:
Number(str) has the same behavior as
str*1, but requires a function call.
I personally use
*1 as it is short to type, but still stands out (unlike the unary +), and either gives me what the user typed or fails completely. I only use
parseInt() when I know that there will be non-numeric content at the end to ignore, or when I need to parse a non-base-10 string.
You can test the performance of these in your browser at my example page.
Global.alert( "base: " + base + ", upfront: " + upfront + ", both: " + (parseInt(base,10) + parseInt(upfront,10)) );
The 10 specifies base 10, otherwise the chance of the value being parsed as octal exists.
That might also be of interest to you. It is just a performance comparison of the methods already mentioned here.
I don't know why the brackets aren't helping you out.
If I try
var base = 500; var upfront = 100; alert("base: " + base + ", upfront: " + upfront + ", both: " + (base + upfront))
I do get 600 as the answer, so it could be there is something going on in the Global.alert function?
One of the mistakes of the language design is that + is both an addition operator and a concatenation operator. Coupled with the fact that it is loosely typed and will cast implicitly means that it can give you some nasty surprises unless you take steps to ensure that you really are adding numbers and not concatenating strings. In this case, it is treating your base + upfront as strings and therefore concatenating.
Anyway, the way around it could be to have
(base - upfront*-1) instead.
It's handling it as a string. You need to do your math before the string. Example:
base + upfront + ' string'
would return "15036 string".
string + base + upfront
would return string 1500036 as you are seeing now.
Or use parseInt().
©2020 All rights reserved.