Re: logic and disabling onclicks?
On Sat, 19 Apr 2008 14:35:51 +0100, Dr J R Stockton
<jrs@merlyn.dem on.co.ukwrote:
John,
Not sure whether you have seen my recent post but just one last point!
Re the conflict with prototype.js - the problem I am told is probably
the use of for/in to iterate over the Next values. It certainly seems
to be so as when I try using the "vanilla" type of iteration I can add
the link to prototype.js and do not get the associated error message.
But! I have tried
for (J=0;J<Next.len gth;++J){
F["B"+Next[J]].disabled = false;
DoSpecificTask[State](F);
}
This is not correct and comes up with "Next has no properties" on
answering the 4th question.
What would be the correct "vanilla" type iteration to replace your
following code?
for (J in Next) F["B"+Next[J]].disabled = false
DoSpecificTask[State](F)
Cheers
Geoff
On Sat, 19 Apr 2008 14:35:51 +0100, Dr J R Stockton
<jrs@merlyn.dem on.co.ukwrote:
>The purpose of my posting that code was not to provide a Final Solution,
>but to show how the routing structure could be compactly represented.
>but to show how the routing structure could be compactly represented.
Not sure whether you have seen my recent post but just one last point!
Re the conflict with prototype.js - the problem I am told is probably
the use of for/in to iterate over the Next values. It certainly seems
to be so as when I try using the "vanilla" type of iteration I can add
the link to prototype.js and do not get the associated error message.
But! I have tried
for (J=0;J<Next.len gth;++J){
F["B"+Next[J]].disabled = false;
DoSpecificTask[State](F);
}
This is not correct and comes up with "Next has no properties" on
answering the 4th question.
What would be the correct "vanilla" type iteration to replace your
following code?
for (J in Next) F["B"+Next[J]].disabled = false
DoSpecificTask[State](F)
Cheers
Geoff
Comment