Yet more gauges

[bnwrx]

Mark, I am using FF 5. I will try your mods but not until tomorrow.

Bob, I am not Mark...

And tomorrow will be fine...

OOPS.... ...

[captzero]

Mark,

Great work..... I'm nearly afraid to ask.... any plans to include a cloud base (linear) gauge?

[gemini06720]

.... any plans to include a cloud base (linear) gauge?

Dan, I am not Mark...

Have you had a chance to look at Gerrit Grunwald's Harmonic Code page ... just to get yourself tempted...

[captzero]

Ray...

I know you are not Mark. Thats why I started my post with Mark and not Ray. My question was directed to Mark (mcrossley) and the compliments were for the efforts and work he has put into the gauges package. I have been to Gerrit Grunwald's site.

[mcrossley]

Hi Dan, no plans for a cloud base gauge yet, but it would be easy to add as a vertical gauge (how about using an aircraft altimeter gauge

Capture.JPG

- if Gerrit ever ports it), but I do have some other little updates in the pipeline.

Today is v0-9, hopefully this will be the last update for a little while. I know Ray is keen to do some more work on translations ans wants a stable release to base it on. So barring any major bugs, this is it for a while.

• Updated gauges.js
  - Fixed scale shading for farenheit temperatures
  - Changed rain and rain rate inches gauges to start range of 0-1 inch
  - Fixed displaying script version in FireFox
  - Fixed 'station offline' code, it was kicking in 10x faster than it should have!
• Updated steelseries.js
  - Added variable decimals to fractionalScale type of radialBargraph gauge

I have also included the un-minified versions of all the scripts in the zip file. They are not required on your website, but are included for reference if you need to change anything.

[bnwrx]

Using new build (v9). Note to Mark, The seconds countdown still does not display correctly with FF5 for me. Ray,your suggestion DOES work for me. I adjusted the number from "13" to "23" and it worked fine.

Bob

[JimDantin]

I've set up the new version and created a new page for it. My navigation still points to the original gauges.htm for now, but check this out:

http://personalpages.bellsouth.net/j/d/ ... auges2.htm

I want to fully integrate the new page into my website, but don't want to edit all the navigation links until I'm sure you guys aren't planning something slicker (hint, hint!) that would allow a new gauge page to supersede the original one.

Thanks for all the development and debug efforts!

[mcrossley]

Using new build (v9). Note to Mark, The seconds countdown still does not display correctly with FF5 for me. Ray,your suggestion DOES work for me. I adjusted the number from "13" to "23" and it worked fine.

Bob

Bob, it works fine for me in FireFox5 too. Have you altered the font settings in FF, or perhaps your Windows desktop (set the text size > 100%)?

[bnwrx]

Using new build (v9). Note to Mark, The seconds countdown still does not display correctly with FF5 for me. Ray,your suggestion DOES work for me. I adjusted the number from "13" to "23" and it worked fine.

Bob

Bob, it works fine for me in FireFox5 too. Have you altered the font settings in FF, or perhaps your Windows desktop (set the text size > 100%)?

Not knowingly to my knowledge. I'll see if I can check somehow.

[bnwrx]

Using new build (v9). Note to Mark, The seconds countdown still does not display correctly with FF5 for me. Ray,your suggestion DOES work for me. I adjusted the number from "13" to "23" and it worked fine.

Bob

Bob, it works fine for me in FireFox5 too. Have you altered the font settings in FF, or perhaps your Windows desktop (set the text size > 100%)?

Another oops..(quite the week for those!) I did not know that the fonts in FF were change. I reset them to the default and also reset the script to "13" and now all is fine. Another Q if I could, in the forecast banner area, it seems to be aligned to the right in the box. Is that as planned? Can it be aligned left or centered?

Thanks

[mcrossley]

The LCD displays are hard coded to be right justified at the moment.

[JimDantin]

The LCD displays are hard coded to be right justified at the moment.

Hopefully that can be changed in the future by some config setting.

I've been playing around with various elements of the page -- can you explain why DELETING the LED, status display or countdown somehow breaks the entire gauge display? If I eliminate those elements I don't see any gauges at all - but the option selectors DO show up. Strange!

[gemini06720]

The LCD displays are hard coded to be right justified at the moment.

Indeed, I looked through the code of the 'steelseries.js' and found the location of the 'hard coded' right justification of the text ... a request for less 'hard coding' and more flexibility would really really be appreciated ... and you have that direct communication/connection with the holy designer...

[beteljuice]

... can you explain why DELETING the LED, status display or countdown somehow breaks the entire gauge display? If I eliminate those elements I don't see any gauges at all ...

I haven't looked at the code, but I suspect it one of those Ajax loop anomalies.

Most errors ocurring within such a loop don't tell you what went wrong, just 'breaks' everything following the error.

One of the common problems is creating / modifying the content of an element without checking to see if it exists first !

As you have deleted a 'named' element but not the associated JS, that sounds like the problem.

Mark to confirm

[mcrossley]

beteljuice is correct, the error checking in the script is very 'light' at the moment. Just deleting elements from the HTML is not sufficient, at the moment you also need to remove/comment out the relevant sections of code that refer to them.

Once I have a solution that functions as expected across the various different unit and nationalisation combinations, I do plan on making it more robust. One obvious addition would be to check for the existence of containers in the DOM before trying to use them. That way people can remove elements easily without having to worry about the code.