Re: F-Keys on 5250 Windows
Posted: Wed Feb 05, 2014 7:18 pm
Ahhh, I see what the problem is. I didn't notice this before, but... you changed the line immediately before the one I asked you to insert.
Here's what it looks like (this is from the screenshot you posted in the RTF file earlier):
So the error messages you posted say that you can't called toLowerCase on line 222, because input.fkey is not defined (and therefore does not have a toLowerCase() method.) This shouldn't ever happen because on line 212, we check if input.fkey==null -- and that will skip any elements where input.fkey is not defined. However, you changed that code on line 212 -- you changed it from input.fkey==null to input.fkey===null (originally it was two equal signs, you changed it to three.)
The problem is, with three equal signs, an undefined element will not be converted to a null for comparison, so the test will no longer find situations where fkey is undefined. With two equal signs it will.
I suspect you did this because the ace editor (the JavaScript editor in the Genie admin) gives a warning when you use two equal signs with null, so you changed it to three, as it suggests. However, in this case, that's not the right thing to do... you'll need to change it back to two equal signs (or change the way it works slightly.)
Here's what it looks like (this is from the screenshot you posted in the RTF file earlier):
- linkmenu4.png (109.28 KiB) Viewed 1444 times
The problem is, with three equal signs, an undefined element will not be converted to a null for comparison, so the test will no longer find situations where fkey is undefined. With two equal signs it will.
I suspect you did this because the ace editor (the JavaScript editor in the Genie admin) gives a warning when you use two equal signs with null, so you changed it to three, as it suggests. However, in this case, that's not the right thing to do... you'll need to change it back to two equal signs (or change the way it works slightly.)