My code seems to be correct..there's no reason why it shouldn't work. And I've written similar instructions b4
FLAW! (Famous LAst Words) That sort of "affirmation" is the first sign that there is some bone-headed typo, forgotten detail, residual code snippet from a prior attempt, logical inconsistency, or whatever, that you can't see because you don't believe it's really there. I run into such cases -- and those same words go through my head -- at least four times a year (used to do it more often, before I got the hang of "use strict"...)
When you get to the point of believing that your code must be right even though it doesn't work, it's time to step through it with the debugger: inspect the values of the variable(s) in question and see how the conditionals behave as you go. That will usually pay off.
| [reply] |
If you could display all of your code it would be very helpful. Sounds like a simple problem, but need to see all the code to debug. | [reply] |
OK, my suggestion would be to try to isolate out the part that isn't working. Perhaps take the code out of the subroutine and see if that might be causing the problem, and so on. | [reply] |