v2.1.0 install

[mcrossley]

As David surmised, you have not updated the gauges-ss.css file to version 2.1...

/* CSS for SteelSeries Gauges
* Mark Crossley
* v2.0.3 - 04 Jan 2013
*/

[dimitris vichos]

its okay now. thankyou.

[mcrossley]

Great.
..and rather embarrassingly, I notice that version 2.1.0 of the css file still has the old v2.0.3 header in it!

[PaulMy]

And to update my status,
I am also as today the SS v.2.1.0 are working fine in both IE and FF on my Windows 8 computer. Nothing I have done other than go to bed and sleep on it... and I guess so did my computer, but no, it doesn't get shut off or go to sleep.

Thanks Mark,
Paul

[water01]

Perhaps the cache got cleared ?

[PaulMy]

Thanks, yes that is what likely happened. I had tried all the normal refresh without any change yesterday but I don't really understand how/where cache is held or when it is cleared. I see that in Mark's Cumulus RealTime Grabber he has a CacheBuster option and I think that overcame a similar issue I had when first installed the Grabber. Is there a way to force to clear cache?

Paul

[water01]

IE9 if you hit F12 the Developer console appears.

Look along the top menu, the sixth one from the left is Cache, click on it and you can either completely clear the browser Cache or Clear Browser Cache for this Domain is relative to the website you hit the F12 button on.

[PaulMy]

Thank you, you have led me to areas previously unknown.
Another checkmark on my what have I learned this week list,

Paul

[mcrossley]

Same in Chrome & FireFox - F12 brings up the Dev tools, which by default are configured to bypass the cache when you refresh the page with the dev tools open.

[water01]

Paul if you are having trouble with some code if you load the page hit F12 and then click on Console in the menu below Cache it will show any errors logged on the page.

HTML will show you the HTML it is running (clicking on the + signs will expand the various pieces).

CSS will show you any style sheets being used.

Script will show you any scripts and does allow some debugging.

Profiling is very interesting if you are really nerdy, allows you to run a page (click on it and then run your web page) and see the times various things took to execute and how many times.

Network is also interesting load your page hit F12 and then Network and say start capturing and then run your page again and you will see the various times it took the Internet to get all your elements to build the page.

Of course if you are not interested it is also a load of garbage!!

[gemini06720]

OK, I have figured out why people are having problems with the odometer positioning (it's all to do with element padding, and an incorrect 'magic number' on my part...

Mark, I know I am late in reporting... ...a guy need some sleep somewhere sometime...

I installed your latest release of 'windrose.js' (2.1.1(test)) - the horizontal centering/positioning is good - the vertical positioning was a bit off for me as I prefer to push the odometer as far down as I can (so it does not remain as obstructive as it is already), by taking it down another 0.05 to 0.75:

Code: Select all

'top': Math.ceil(_odoParent.outerHeight() * 0.75) + 'px',

It is really too bad that the odometer could not be digital (rather than mechanical) - similar to the LED digital displays inside the other gauges - even modern cars do not use mechanical odometers any more...

[mcrossley]

Ray, sad that I am I thought in bed last night that the solution I came up with yesterday is not robust in all situations. So I thought of a better way of doing it, which I have coded this morning. See below...

Aw, you don't like my odometer, I was proud of that implementation.
I know other people do like it, and the advantage that I can see is that it is instantly recognisable as a distance indicator rather than just 'some number'. The other reason it that is already available as a gauge object.

There is no reason you couldn't use a 'DisplaySingle' like the timer on the page, which can also have a suffix for units, but you would lose the 'animation' of the value changes unless you implement it yourself.

windrose.js

[water01]

New one works OK for me Mark.

[mcrossley]

Thanks David.

[gemini06720]

Aw, you don't like my odometer, I was proud of that implementation.

Mark, Mark, it is not that I dislike (completely ) the odometer - you really did a good job, not only for the odometer but for all the gauges. But, but ... a mechanical (looking) odometer look so much like the 60s (again, nothing wrong with the 60s ) while the rest of the gauges look so much like the 13s...

The other reason it that is already available as a gauge object.

I also understand that point - Mark, if I really, and I mean really did not like the odometer 'one-little-bit', I would not activate its display...

There is no reason you couldn't use a 'DisplaySingle' like the timer on the page...

Mark, this would go a bit too far out of my comfort zone ... considering that I still have many old templates to adapt/convert to the underdevelopment web site...

Oh, now the less good news - the newer version of the 'windrose.js' script did not solve my situation (you can check on the new site if you want as I have placed the (almost) non-modified version of the latest script (the only modification was to give the wind rose gauge a size of 295) - the odometer is now too high and off-centered to the left...