Timing problem on (overly) complex page.

[julie.siebel]

Google apparently ate my original post to this (grr) so this'll be a
bit more vague than the initial post, but...*sigh*.

Javascript is not my forte, and I apologize for the acky-ness of the
code.

I'm working on a page for a travel company. There's way too much going
on with it/on it, but I'm kind of stuck at this point - the client
loves it, so I have to solve this problem.

http://www.untours.com/samplerstage2...29&Code=07STSH

It *almost* works, or I should say, almost always works, but if you
click "clear all" (which calls the showall() function) then click a
date very quickly afterward, the date gets stuck - no amount of
clicking on a date (pickdate() function) will make the link work, but
clicking on any OTHER date, will reset stuff so everything works fine.
This also happens (a lot less often) when you click on a property name/
pic (showdesc()) then jump to a date.

The HTML generated by the page (It's 10k of SQL, 4k of VBScript and a
zillion lines of javascript) validates, and the javascript isn't
generating any errors. (The page has only been tested thusfar in
Firefox 2.0 and IE6.)

It's obviously some sort of a timing issue, but I'm not sure how to
handle it. I searched the newsgroup, but nothing seemed to apply. (If
anyone could point out a good thread, that'd be great.)

I tried adding an activity indicator that temporarily overwrote the
date section, by adding code to the end of the showall() function, but
the function just blows right by it, as if it had completed its work.

I thought it might be the pickdate() function instead (though I
couldn't see how), so I added an alert to the beginning of that
function to kinda "slow it down" as a test. When you do the quick
click, though, it never sees the first line of the pickdate()
function.

There is a LOT (as in "way too much") going on in this page, so it's
not exactly speedy, especially the way that I write. The page is huge,
kb-wise. (I try to keep pages to 80k or so absolute max - when
downloaded on a 56k modem, that's about the time it takes for the
telephone to ring 4 times). I'm sure I boogered up something and/or
broke all kinds of javascript rules. I'm at a loss here. Anyone have
an idea of how to resolve a timing issue like this? (Just wish it
weren't so darn intermittent.)

Thanks in advance, and again, apologies for the state of the
javascript.

Julie

[Darko]

On Jun 26, 7:15 am, "[e-mail]" <[e-mail]>
wrote:

Google apparently ate my original post to this (grr) so this'll be a
bit more vague than the initial post, but...*sigh*.

Javascript is not my forte, and I apologize for the acky-ness of the
code.

I'm working on a page for a travel company. There's way too much going
on with it/on it, but I'm kind of stuck at this point - the client
loves it, so I have to solve this problem.

http://www.untours.com/samplerstage2...29&Code=07STSH

It *almost* works, or I should say, almost always works, but if you
click "clear all" (which calls the showall() function) then click a
date very quickly afterward, the date gets stuck - no amount of
clicking on a date (pickdate() function) will make the link work, but
clicking on any OTHER date, will reset stuff so everything works fine.
This also happens (a lot less often) when you click on a property name/
pic (showdesc()) then jump to a date.

The HTML generated by the page (It's 10k of SQL, 4k of VBScript and a
zillion lines of javascript) validates, and the javascript isn't
generating any errors. (The page has only been tested thusfar in
Firefox 2.0 and IE6.)

It's obviously some sort of a timing issue, but I'm not sure how to
handle it. I searched the newsgroup, but nothing seemed to apply. (If
anyone could point out a good thread, that'd be great.)

I tried adding an activity indicator that temporarily overwrote the
date section, by adding code to the end of the showall() function, but
the function just blows right by it, as if it had completed its work.

I thought it might be the pickdate() function instead (though I
couldn't see how), so I added an alert to the beginning of that
function to kinda "slow it down" as a test. When you do the quick
click, though, it never sees the first line of the pickdate()
function.

There is a LOT (as in "way too much") going on in this page, so it's
not exactly speedy, especially the way that I write. The page is huge,
kb-wise. (I try to keep pages to 80k or so absolute max - when
downloaded on a 56k modem, that's about the time it takes for the
telephone to ring 4 times). I'm sure I boogered up something and/or
broke all kinds of javascript rules. I'm at a loss here. Anyone have
an idea of how to resolve a timing issue like this? (Just wish it
weren't so darn intermittent.)

Thanks in advance, and again, apologies for the state of the
javascript.

Julie

I tried it, but I have no problems with it... I clicked on the "Clear
sampler", then quickly (as quickly as my hands can, though.
Nevertheless...) on any date, and tried it several times, but no
problem have I found... Maybe my computer is too fast? Or maybe yours
is slow? :)

[julie.siebel]

On Jun 26, 12:49 am, Darko <[e-mail]:

On Jun 26, 7:15 am, "[e-mail]" <[e-mail]>
wrote:

Google apparently ate my original post to this (grr) so this'll be a
bit more vague than the initial post, but...*sigh*.

Javascript is not my forte, and I apologize for the acky-ness of the
code.

I'm working on a page for a travel company. There's way too much going
on with it/on it, but I'm kind of stuck at this point - the client
loves it, so I have to solve this problem.

http://www.untours.com/samplerstage2...29&Code=07STSH

It *almost* works, or I should say, almost always works, but if you
click "clear all" (which calls the showall() function) then click a
date very quickly afterward, the date gets stuck - no amount of
clicking on a date (pickdate() function) will make the link work, but
clicking on any OTHER date, will reset stuff so everything works fine.
This also happens (a lot less often) when you click on a property name/
pic (showdesc()) then jump to a date.

The HTML generated by the page (It's 10k of SQL, 4k of VBScript and a
zillion lines of javascript) validates, and the javascript isn't
generating any errors. (The page has only been tested thusfar in
Firefox 2.0 and IE6.)

It's obviously some sort of a timing issue, but I'm not sure how to
handle it. I searched the newsgroup, but nothing seemed to apply. (If
anyone could point out a good thread, that'd be great.)

I tried adding an activity indicator that temporarily overwrote the
date section, by adding code to the end of the showall() function, but
the function just blows right by it, as if it had completed its work.

I thought it might be the pickdate() function instead (though I
couldn't see how), so I added an alert to the beginning of that
function to kinda "slow it down" as a test. When you do the quick
click, though, it never sees the first line of the pickdate()
function.

There is a LOT (as in "way too much") going on in this page, so it's
not exactly speedy, especially the way that I write. The page is huge,
kb-wise. (I try to keep pages to 80k or so absolute max - when
downloaded on a 56k modem, that's about the time it takes for the
telephone to ring 4 times). I'm sure I boogered up something and/or
broke all kinds of javascript rules. I'm at a loss here. Anyone have
an idea of how to resolve a timing issue like this? (Just wish it
weren't so darn intermittent.)

Thanks in advance, and again, apologies for the state of the
javascript.

Julie

I tried it, but I have no problems with it... I clicked on the "Clear
sampler", then quickly (as quickly as my hands can, though.
Nevertheless...) on any date, and tried it several times, but no
problem have I found... Maybe my computer is too fast? Or maybe yours
is slow? :)- Hide quoted text -

- Show quoted text -

Eh - hard to say! I'm pretty quick on the clicking (as I have been
working on this mess for quite a while now - lol), and I don't *think*
a client would click that fast, but it's kind of disconcerting when it
does happen. It's driving me nuts. I tried it both in IE and Firefox
and it does the same thing, so doesn't appear to be browser specific.
My computer is *reasonably* fast, though not a speed demon, but a lot
of this client's clients have slooowww boxes.

Anybody out there with a slow computer want to give it a shot? :P

It *has* to be timing. I just don't know what to *do* about it.

Thanks for checking, anyway.

Julie