The beteljuice is unhappy with the logic order - there seems to be a lot of unecessary work being done !
I haven't looked at any of the original code, but am assuming:
This code is already in a loop where each 'line' of data is being processed
Each line has already been split into 'col' components - wd_data[x] - where x = dayfilecol
You wish to make a decision based on content
type - dayfilecol value - (eg. 4 = Min temp)
but the first 'enquiry' is the
value of the data regardless of
type (ie. EVERY record entry), this would sort of be OK for a single type check, but is escalating because of all the multiple type checks.
The original code snippet was not incorrect because it
was looking for
any zero value of data.
So this:
Code:
// Max Temp
if((parseFloat(wd_data[dayfilecol])>=37.0)&&(dayfilecol==6)) {$(data_cell).addClass('extremehigh');}
Would be better as:
Code:
// Max Temp
if((dayfilecol==6) && (parseFloat(wd_data[dayfilecol])>=37.0)){$(data_cell).addClass('extremehigh');}
Also, in the case of temp, your colour decisions are identical for Max / Min, so no need to duplicate the code just:
Code:
// Min / Max Temp
if((dayfilecol==4 || dayfilecol==6) && (parseFloat(wd_data[dayfilecol])>=37.0)){$(data_cell).addClass('extremehigh');}
and so on ... having just ONE block of code
Perhaps daj could please cast an eye and either confirm or delete the musings of the beteljuice ...
Login 
Register
Enhancement requests
Search
When I tried "break;" in various places, it just resulted in no data being posted.