Trixology
WeatherCat => WeatherCat Web Templates => Topic started by: Blicj11 on February 10, 2015, 07:27:48 AM
-
I upgraded to SteelSeries 2.5.4 today. I had been using 2.4.x and I really like the improvements Mark. Thanks for the new cloudbase gauge for WeatherCat users and all the other improvements.
I have one small problem that really puzzles me. In my temperature gauges, instead of the gauge face displaying "?F" I am getting "?F".
I know that happens if you edit the gauges.js file with something that does not preserve UTF-8 code format or if the host page does not support UTF-8. However, I don't think either of these apply to me. I edited the files with TextWrangler 4.5.12 and I made sure I saved the files in UTF-8. This is the text editor I have always used on the SteelSeries files and have never had a problem. I made no other changes to the hosting page other than to point to the new directory I uploaded containing the upgraded SteelSeries folders and files.
I tried using TextEdit and Jedit and neither of them solved the problem.
I see that Reinhard does not have this issue. Reinhard, what do you edit with?
Mark, is there any other reason I am getting the errant degree sign?
http://timberlakesutah.com/weather/
-
Hi Blick,
I am using TextWrangler, too. Indeed a bit strange, that those ? are not shown correct. Maybe Mark can give you an advice for this one. Another thing that I noticed is you can display a Cloud Base Graph when you hover the Cloud Base Gauge: WeatherCat provides it and it is called cloudbase1.jpg - if you want to use it just take care that this simple graph is uploaded!
Cheers,
Reinhard
-
Another thing I found on Mark's Wiki:
http://wiki.sandaysoft.com/a/SteelSeries_FAQ#I_get_funny_symbols_on_the_gauges_before_the_degree_sign
Is that of help for you?
-
Reinhard:
I am already uploading cloudbase1.jpg but when I hover over the gauge I am getting a pressure graph. Do I need to make a change in one of the files to get clpudbase1.jpg to show up properly?
-
Another thing I found on Mark's Wiki:
http://wiki.sandaysoft.com/a/SteelSeries_FAQ#I_get_funny_symbols_on_the_gauges_before_the_degree_sign
Is that of help for you?
I already looked at this before I posted. I don't think either one of them applies, but maybe the host page is the problem, although I have not made any changes to it that I know of.
-
OK. I figured out the cloudbase1.jpg issue. In the gauges.js file, there is an error on line 280. This is where the graph is defined for what pops up when you hover over the cloudbase gauge. It calls for the pressure1.jpg. Replace "pressure1.jpg" with "cloudbase1.jpg" and the proper graph pops up. Thanks for looking at my site Reinhard, I had missed that one.
Now, if I can just figure out why "?F" is being replaced by "?F" I'll be happy camper.
-
Sorry Blick for my unclear advice with cloudbase1.jpg - I should have told you where you find it in gauges.js :-[
Hopefully you get this ?F sorted out, if I notice something I will tell you immediately.
Cheers,
Reinhard
-
Sorry Blick for my unclear advice with cloudbase1.jpg - I should have told you where you find it in gauges.js :-[
No worries. After I thought about it for a couple of minutes I had an idea where to look and it was easy to find. You've been a big help. Thanks again.
Now I'm going to bed! 02:00 is late enough for this day's weather hobby. :)
-
Success - I found it:
In the new (2.5.4) gauges.js on line 3707 and line 3719 there is a difference to the (2.4.4) gauges.js - look at the screenshots.
Just replace the '?' to a '?' and you should be done! What I don't know is if we are breaking something in this script by doing this - here on my side it looks ok after changing ? to ? :)
Cheers,
Reinhard
-
Reinhard:
How do you keep scoring these brilliant goals? ⚽
I made the changes on lines 3707 and 3719 and it works! As you say, we may have broken something else but it looks like its working to me. We'll have to wait for Mark to tell us if we are making things worse.
-
Mark:
I appreciate the improvements you continue to make to the SteelSeries. Thanks for you efforts.
I have two more questions.
- I have turned off the optional display of the wind variation on the direction gauge but it continues to display that information anyway. Is there some place other than the line for showWindVariation I need to check?
- We haven't had much sun, but the LED does not light up when we do. I do have the showSunshineLed set to true. What is the criteria for the LED light turning on to indicate the sun is shining on the solar gauge?
Thanks.
-
1. Give line 58 a try and set it to 'false' - no need to do something in 'showWindVariation'
2. Read through the lines 101 and 102.
;)
Hope this helps.
Reinhard
-
First, apologies for the ?C & ?F - the file diff tool I was using seems to have mangled the UTF-8, I'll have to see if there is an option to handle it properly - or look for a new tool.
1. I'll look into that now...
2. Lines 101 & 102,
sunshineThreshold : 50, // the value in W/m? above which we can consider the Sun to be shining, *if* the current value exceeds...
sunshineThresholdPct : 75, // the percentage of theoretical solar irradiance above which we consider the Sun to be shining
-
By the way, Blick, I admire your windrose gauge - it shows only a few wind directions. Mine shows a chaos - wind arriving from all directions!
Cheers,
Reinhard
-
Sorry Mark,
haven't seen your posting.
Reinhard
-
Mark:
I appreciate the improvements you continue to make to the SteelSeries. Thanks for you efforts.
I have two more questions.
- I have turned off the optional display of the wind variation on the direction gauge but it continues to display that information anyway. Is there some place other than the line for showWindVariation I need to check?
- We haven't had much sun, but the LED does not light up when we do. I do have the showSunshineLed set to true. What is the criteria for the LED light turning on to indicate the sun is shining on the solar gauge?
Thanks.
I think the Sun question has been answered, so, wind variation. I just tested it and it works for me, but I think you may be confusing to different features.
showWindVariation enables shading at the edge of the gauge to show the variation in direction in the last 10 minutes.
showRoseOnDirGauge enables showing a 'type' of wind rose on the direction gauge background. Rather than the length of the segment showing the relative strength from a particular direction, the depth of colour and transparency are used.
I'd suggest you switch off showRoseOnDirGauge and leave showWindVariation on and see how you like it - that is how 2.4 worked.
-
Reinhard and Mark:
Thanks for your replies. I am now properly instructed on the wind direction and solar gauges. I am up and running on the new SteelSeries gauges. I think they look great. Thank you both for your help.
-
I am attempting to understand what is being displayed on each gauge and have a few questions. Might someone either answer them or point me to someplace on the web where I might find the answers?
- Generally, are the red bands on the gauge faces (temperature, humidity, pressure, solar) showing the range of the past 24 hours or the range of Today only?
- What is being displayed on the red and green bands on the Wind Speed gauge? I assume green is 10-minute average and red is 10-minute wind gust, but since it is a band I'm not sure what the range is displaying.
- Which average is displayed by the secondary needle on the Wind Direction gauge? I assume 10-minute.
- Are the dark red bands on Pressure the all-time historical high and low range?
Thanks.
-
The gauges can only display data they were feeded with our realtimegaugesWC.txt file, so at least your first question I think I can answer: It is the TODAY$ tag that is used. Maybe some more of your questions are hidden in this file which feeds the gauges.
May I add another question to Mark:
5. When ledVisible is set to 'true', when do they blink (alert?) and when do they stay dark (not blinking)?
Cheers,
Reinhard
-
and I have one more question.
6. What is being displayed in the red band on the Wind Direction? My entire 360? is shaded red today. What does that mean?
Thanks.
-
Noticed this anomaly: Sometimes the red range band on the Wind Direction gauge looks like the bands on the other gauges and sometimes it just covers the edge. See attached screen shots. Any idea why?
-
I am attempting to understand what is being displayed on each gauge and have a few questions. Might someone either answer them or point me to someplace on the web where I might find the answers?
- Generally, are the red bands on the gauge faces (temperature, humidity, pressure, solar) showing the range of the past 24 hours or the range of Today only?
- What is being displayed on the red and green bands on the Wind Speed gauge? I assume green is 10-minute average and red is 10-minute wind gust, but since it is a band I'm not sure what the range is displaying.
- Which average is displayed by the secondary needle on the Wind Direction gauge? I assume 10-minute.
- Are the dark red bands on Pressure the all-time historical high and low range?
Thanks.
2. Yes, green shows average STAT$WINDSPEED:AVERAGE:HRS(0.17)$, red gust STAT$WINDGUST:MAX:HRS(0.17)$
3. Yes, average STAT$WINDDIRECTION:AVERAGE:HRS(0.17)$
4. Yes.
-
The gauges can only display data they were feeded with our realtimegaugesWC.txt file, so at least your first question I think I can answer: It is the TODAY$ tag that is used. Maybe some more of your questions are hidden in this file which feeds the gauges.
May I add another question to Mark:
5. When ledVisible is set to 'true', when do they blink (alert?) and when do they stay dark (not blinking)?
Cheers,
Reinhard
Do you mean the standard SS gauge property? If so it blinks when the current value exceeds the threshold value, the threshold value is set to 50% of the gauge range by default - until you override it.
-
Noticed this anomaly: Sometimes the red range band on the Wind Direction gauge looks like the bands on the other gauges and sometimes it just covers the edge. See attached screen shots. Any idea why?
The red bands show the variation in direction in the last 10 minutes. It is show as a thin band on the scale if the average speed is below 3 knots (aviation threshold for 'variable' in Europe), sectors if above 3 knots.
-
Do you mean the standard SS gauge property? If so it blinks when the current value exceeds the threshold value, the threshold value is set to 50% of teh gauge range bye default - until you override it.
Got it - thanks for explaining! :)
Reinhard
-
Thanks for the explanations Mark. And again, thanks for the improvements to the SteelSeries for WeatherCat users.
-
Hi Blick, Rheinhard, and Mark
I have up date to the latest version 2.5.4 but the ticker is not scrolling any more and I can't get the cloud base gauge to show up
So what am I doing wrong?
Thanks for your help
UPDATE: Got the ticker to scroll but it is not downloading as before to update the dated and still can not get the CloudBase Gauge to show up
PS Getting this error ever once in a while:PARSERERROR: SYNTAXERROR: JSON PARSE ERROR: UNEXPECTED EOF
cheers [cheers1]
-
Hello Randall,
just viewed your site and it seems that you are using gauges.js V 2.5.2 and not V 2.5.4?
Cheers,
Reinhard
-
Hi Rheinhard
That's what it says but I down loaded at the latest version and uploaded it
cheers
If not where do I get 2.5.4?
-
Here you can download the latest version: http://wiki.sandaysoft.com/a/SteelSeries_Gauges#Downloads
-
Hi Reinhard
After my last posting I went back and downloaded it again and redone everything and now after about 5 hours I have it working thanks for your post was just about to give up never had problems before with the Steel Gauges
CHEERS [cheers1]
-
Randall:
I just took a look at your gauges and you still have two minor issues you need to correct.
- The 2.5.4 download has an error in guages.js around line 280. This is where the graph is defined for what pops up when you hover your mouse over the cloudbase gauge. It currently calls for the pressure1.jpg. Replace pressure1.jpg with cloudbase1.jpg and the proper graph will pop up.
- This line at the bottom of your gauges page has two typos: It is use to compare weather data to other PWS, NOAA and NWS reporting stations in area. I think you intended to say this: It is used to compare weather data to other PWS, NOAA and NWS reporting stations in the area.
I like Mark's improvements. The yellow LED on the solar gauge when the sun is shining is very cool.
-
Mark:
I hope you don't mind if I pose another question.
In order for the "sun is shining" LED on the Solar gauge to turn on, do both of the criterion in Line 101 and 102 (gauges.js) have to met or is it one of the two have to be met?
See attached.
Thanks.
-
Hi Blick
Thanks I'll get it corrected
cheers [cheers1]
-
Mark:
I hope you don't mind if I pose another question.
In order for the "sun is shining" LED on the Solar gauge to turn on, do both of the criterion in Line 101 and 102 (gauges.js) have to met or is it one of the two have to be met?
See attached.
Thanks.
Both have to be met.
The 'Threshold' is to stop the attempt at sunshine detection when the readings are very low near dawn/dusk - very often the sensors read higher than expected at this time due to the cosine response not being totally accurate, and atmospheric scattering from dust and cloud having a relatively large effect.
So once the value current value exceeds the threshold, then it also has to equal or exceed the percentage of theoretical before we declare 'sunshine'!
These values can be tuned to your location and sensor.
-
BTW, I just uploaded 2.5.5 to GitHub to fix the errors reported in 2.5.4 here. I also added config options for changing the Wind Direction average pointer type and colour.
-
Thanks Mark!
Looking great, working great.
Reinhard
-
BTW, I just uploaded 2.5.5 to GitHub to fix the errors reported in 2.5.4 here. I also added config options for changing the Wind Direction average pointer type and colour.
Thanks for the quick turnaround on this Mark and for adding the config options for the secondary needle on the Wind Direction Gauge. I am now running 2.5.5 and have made a slight tweak in the WeatherCat wiki entry to reflect updated line numbers to edit in gauges.js
-
Mark,
now it's up to me to post a question:
What is the difference between the thin and thick pointers in the Windrose gauge? As example I compared yours (thick) to mine (thin), see attachment.
Thanks,
Reinhard
-
It is purely a function of how many wind direction 'buckets' your software is providing. I have Cumulus configured to provide 16 directions (N, NNE, NE, ENE, E etc), it looks like you have 32 or more?
-
Mark:
I too have another question. I made some minor changes in gauges-ss-basic.htm and FTP'd to my site. Unlike edits in the gauges.js, which are immediately visible after FTP, these changes did not appear. After triple checking and re-FTPing, they still did not show up. I waited overnight and they still were not visible. I then flushed to cache in my brower, which resulted in two things:
- The changes in gauges-ss-basic.htm now properly display
- The change I had made in gauges-ss.css to use a different background jpg was no longer in effect
I re-edited the gauges-ss.css file and after FTPing it to my site the SteelSeries gauges displayed properly.
Apple made a change to Safari in that you can no longer empty cache and history separately. You now have to fluke everything together. I used the option of flushing cache and history from today and yesterday.
I'm still not sure what the gauges-se-basic.htm did not display even though the edited code was clearly in the file.
Do you have any thoughts on what happened to me or what I should have done?
Thanks.
-
It is purely a function of how many wind direction 'buckets' your software is providing. I have Cumulus configured to provide 16 directions (N, NNE, NE, ENE, E etc), it looks like you have 32 or more?
If you are talking about line 2147, I also have 16 spokes, but my gauge shows the thin lines like Reinhard's. Mine are even thinner. See attachments. Is it just the background of the gauge?
UPDATE: I see I am talking about something else. I was referring to the fixed lines and you are talking about the "wind pattern buckets" themselves.
-
It is purely a function of how many wind direction 'buckets' your software is providing. I have Cumulus configured to provide 16 directions (N, NNE, NE, ENE, E etc), it looks like you have 32 or more?
THANKS for this one, after you explained the why I realized the how! WeatherCat provides two tags for the 'WindRoseData' read out from realtimegaugesWC.txt in your script: 'WINDROSE8$' (provides 8 directions every 45?) and 'WINDROSE45$' (provides 45 directions every 8?). So mine was set at the higher resolution, after setting to lower resolution the pointers are 'thick'. :D
Thanks again for this hint,
Reinhard
-
THANKS for this one, after you explained the why I realized the how! WeatherCat provides two tags for the 'WindRoseData' read out from realtimegaugesWC.txt in your script: 'WINDROSE8$' (provides 8 directions every 45?) and 'WINDROSE45$' (provides 45 directions every 8?). So mine was set at the higher resolution, after setting to lower resolution the pointers are 'thick'. :D
Nice catch Reinhard. The default for realtimegaugesWC.txt is 'WINDROSE45$. I also changed mine and I agree with you: 'WINDROSE8$' is better.
-
No option for 16? That is the the de facto standard for wind roses as far as I can see. The Fine offset stations are spec'd to report 16, but in fact only really report 8 due to bad design.
-
Actually, it looks like WINDROSE8$ is actually supplying 16 data points?
-
Just 8 - here my current output:
Windrose 8: 0.0,0.0,0.0,0.0,0.0,13.9,25.6,0.0
(from http://live.trixology.com/custom/)
I'm guessing comma decimal point separator? Could you check the output on your system please Reinhard?
If it is this, I can fix it in the next build.
-
Just 8 - here my current output:
Windrose 8: 0.0,0.0,0.0,0.0,0.0,13.9,25.6,0.0
(from http://live.trixology.com/custom/)
I'm guessing comma decimal point separator? Could you check the output on your system please Reinhard?
If it is this, I can fix it in the next build.
Looking at Reinhard's realtimegaugesWC.txt it does seem to be using a comma for both the list separator and the decimal. Explains why the Windrose45 option produced such small sectors - it was being interpreted as 90 values.
-
Here is my data using WINDROSE8$: "WindRoseData":[0.0,0.0,0.0,2.0,0.0,0.9,53.2,42.6],
This is what is looks like with WINDROSE45$: "WindRoseData":[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.8,1.1,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.1,0.1,0.2,0.1,0.7,1.5,3.5,6.7,16.3,18.9,15.5,12.5,10.7,7.4,2.4,0.0],
-
I'm guessing comma decimal point separator? Could you check the output on your system please Reinhard?
If it is this, I can fix it in the next build.
I have been already asleep when you posted this, so my answer is a bit delayed. Here is the output of my 'WINDROSE8$' (today we have had zero wind till now):
"WindRoseData":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],
Looking at Reinhard's realtimegaugesWC.txt it does seem to be using a comma for both the list separator and the decimal. Explains why the Windrose45 option produced such small sectors - it was being interpreted as 90 values.
Thank you for looking at this. You are right, Mark, in the German version of WeatherCat we use a decimal comma, not a decimal point. Therefore 'WINDROSE8$' shows 16 values, and 'WINDROSE45$' showed 90 values.
Stu,
would be great if you can fix this one. Is it possible to have only this output in decimal points and leave all others (statistics, graphs, etc.) with a decimal comma?
Cheers,
Reinhard
-
Another thought, Stu:
I don't know how much effort it will take but have you thought about about using an integer for this one - then there will be no decimal sign needed?
Cheers,
Reinhard
-
Mark:
I have two more questions.
- What is the red band on the Solar Radiation gauge displaying? I know it is a range, but what range is it? I have looked at the tags but still can't figure out what time period and what variable this is.
- In case you missed this, please take a look at http://athena.trixology.com/index.php?topic=1585.msg13417#msg13417
Thanks for your patience.
-
To get readable data for the processed realtimegaugesWC.txt file I went to System Preferences, and turned on a '.' instead of ',' as decimal separator. Now the output is readable for the windrose gauge:
"WindRoseData":[0.5,1.4,0.1,4.7,4.3,1.0,0.5,0.5],
All other data logically are processed now with '.' instead of ',' (Stats, NOAA, ...).
Cheers,
Reinhard
-
The lower limit of the red band on the solar gauge indicates the calculated solar max value, so if you stray into the band you are reading > 100% of theoretical. Nothing wrong with that, there are valid reasons for why it happens, primarily reflections.
Sorry, I have no idea about your editing issues other than the browser is caching stuff. I might say 'use a decent browser!' ;) - I'm a fan of Chrome, primarily because I like the debugging and dev tools in it.
-
Hi Reinhard
Did you do that in the Language and Region of the System Preferences?
cheers [cheers1]
-
Hi Randall,
yes!
Cheers,
Reinhard
-
The lower limit of the red band on the solar gauge indicates the calculated solar max value, so if you stray into the band you are reading > 100% of theoretical. Nothing wrong with that, there are valid reasons for why it happens, primarily reflections.
Sorry, I have no idea about your editing issues other than the browser is caching stuff. I might say 'use a decent browser!' ;) - I'm a fan of Chrome, primarily because I like the debugging and dev tools in it.
Thanks Mark. I have been experimenting with the threshold values and the "sunlight" LED. I think I have it working pretty well for clear winter days but I wonder if I will have to raise the values during the summer. Also need to see what a really cloudy day does to my current lower threshold values.
I appreciate your teaching us about this great piece of software. I intend to take some time and and incorporate this into the WeatherCat version of the SteelSeries Wiki so you don't have to keep repeating yourself.
Your comment about using a decent browser gave me good laugh. I used to use other browsers, but I really appreciate the ability Yosemite and iOS 8 give me to pull up, open and close Safari browser tabs across devices.
-
Your comment about using a decent browser gave me good laugh. I used to use other browsers, but I really appreciate the ability Yosemite and iOS 8 give me to pull up, open and close Safari browser tabs across devices.
Chrome does that too ;)
-
Here is something odd. Look at the screenshot of my Apparent Temp gauge. The digital display is correct but the auto scale is crazy. It probably wouldn't have happened in Chrome. ;)
-
Well, you're right, it doesn't display like that in Chrome ;)
Best thing to do if this sort of thing happens is to capture a copy of the realtimegaugesWC.txt file - there is probably something in there causing it - it looks like the problem has cleared now?
-
Hi Blick and Mark
Not having any problem with it here
CHEERS [cheers1]
-
Best thing to do if this sort of thing happens is to capture a copy of the realtimegaugesWC.txt file - there is probably something in there causing it - it looks like the problem has cleared now?
I should have thought of that. Next time ...
And you are right, it cleared itself up within a few minutes.
I really like the 2.5 improvements and have been studying the gauges.js file to see what I can tweak. Thank you again, for a brilliant piece of software and for accommodating WeatherCatters.
-
I am looking at the popup graphs and I notice that Reinhard and I (and most of the other WeatherCat installations of SteelSeries, display a popup graph that displays the time in HH:MM. However, Randall, has popup graphs (except for Cloud Base) that display the time in whole hours with no minutes. Where is this being controlled, in a SteelSeries file or in WeatherCat preferences?
Thanks.
-
Well it's not in the SteelSeries ;)
-
Well it's not in the SteelSeries ;)
OK Randall, how are you doing it?
-
Hi Blick and steel gauge specialist
Blick are you using basic graphs or custom graphs?
If your are using custom graphs like me they need to be Type: Anchored Data to get to just hours if Scrolling Data it will show minutes
I just went in and changed my cloud base to anchored to match the rest of my graphs
cheers [cheers1]
-
Ah ha. Thank you Randall. I am just using the basic graphs so thanks for the explanation. I may give the custom graphs a whirl. They look better in the popup window.
-
Mark:
A couple of new questions:
- In version 2.4.4 we changed gauge size by editing the gauges-ssT.htm and changing the gaugeSizeStd parameter. In 2.5.x there is no gauges-ssT.htm file and I cannot find this parameter in the other files: <canvas id="canvas_dew" class="gaugeSizeStd"></canvas>. Is there a new way to change gauge size?
- If I want to play with adding a new gauge, like the clock, is the general idea that I copy the entire Clock section from the Canvas-master/steelseries.js file into the 2.5.5 steelseries.js file or do I replace the entire file?
Thanks.
-
Hi Blick,
maybe with your first question I can help: As far as I understand this one you can only give the gauge size three parameters: 'gaugesSizeSml', 'gaugeSizeStd' and 'gaugeSizeLrg'. Those sizes are predefined within the 'gauges-ss.css' file. If you want to alter the size just change the desired parameter in this file.
Your second question is very interesting - I too am interested in building the clock-gauge into my live gauges page. ;)
Cheers,
Reinhard
-
Mark:
A couple of new questions:
- In version 2.4.4 we changed gauge size by editing the gauges-ssT.htm and changing the gaugeSizeStd parameter. In 2.5.x there is no gauges-ssT.htm file and I cannot find this parameter in the other files: <canvas id="canvas_dew" class="gaugeSizeStd"></canvas>. Is there a new way to change gauge size?
- If I want to play with adding a new gauge, like the clock, is the general idea that I copy the entire Clock section from the Canvas-master/steelseries.js file into the 2.5.5 steelseries.js file or do I replace the entire file?
Thanks.
1. Yes, as pointed out this is now defined in the CSS file - with a three pre-defined for you.
2. If you are confident, then just adding the clock gauge code should do it, if not use the full SteelSeries library. Remember that by default the gauges use a combined file consisting of minimised versions of the cut-down SS lib + the twen lib.
-
Thanks Reinhard and Mark.
maybe with your first question I can help: As far as I understand this one you can only give the gauge size three parameters: 'gaugesSizeSml', 'gaugeSizeStd' and 'gaugeSizeLrg'. Those sizes are predefined within the 'gauges-ss.css' file. If you want to alter the size just change the desired parameter in this file.
1. Yes, as pointed out this is now defined in the CSS file - with a three pre-defined for you.
I understand the three pre-defined sizes and I do not want to change any of them. What I don't understand is where do I change my gauges from Medium to Large?
2. If you are confident, then just adding the clock gauge code should do it, if not use the full SteelSeries library. Remember that by default the gauges use a combined file consisting of minimised versions of the cut-down SS lib + the twen lib.
Ha ha. Well, I 'm not too confident and I do understand that you don't support additional gauges outside your subset of the library. Is there someplace we can go read about how the gauges work or is it just trial and error?
-
What I don't understand is where do I change my gauges from Medium to Large?
Just go to your html file that shows the steel gauges and change the 'class' of the gauges you want to have bigger or lesser. :)
Update: Change all of them, not only the one I circled... ;)
-
Just go to your html file that shows the steel gauges and change the 'class' of the gauges you want to have bigger or lesser. :)
Update: Change all of them, not only the one I circled... ;)
Ah ha! I had looked in the gauges-ss-basic.htm file but didn't see the code because I started my search down below all of these gauges and I thought the Find tool would wrap back around and find something earlier in the document. Anyway, sorry to be such an eejit. I get it now and have successfully changed my gauges to the larger size. Thanks for your assistance.
Reinhard, I have figured out how to change the font and color of the credits at the bottom of the gauges. I have also changed the background color of the Units of Measure table. Can you tell me where you changed the font for the radio buttons, such as Inside, Outside, Wind Chill, Apparent, etc., as well as the Units of Measure radio buttons?
Thanks.
-
Mark:
I have a repeat of the weird scaling on the Apparent Temp Gauge. See attached screenshot of the gauge and copy of the realtimeguagesWC.txt file. Do you see anything in the txt file that could be causing this?
-
Reinhard, I have figured out how to change the font and color of the credits at the bottom of the gauges. I have also changed the background color of the Units of Measure table. Can you tell me where you changed the font for the radio buttons, such as Inside, Outside, Wind Chill, Apparent, etc., as well as the Units of Measure radio buttons?
Thanks.
I will try. In your case go to your 'gauges-ss.css' - in there you have to change the font family to your desired font:
body {
font-family: Verdana, Helvetica, sans-serif;
font-size: 10pt;
text-align: left;
background-image: url(http://timberlakesutah.com/wp-content/uploads/Weather/SteelSeries/images/brushedsteel2.jpg);
color: #323232;
}This will change the font in your whole 'gauges-ss-basic.html' except the ones you specified separately (i.e. the one you gave the class '.credits').
If you want to change the font in the tool tips of the opening graphs on hovering a gauge, you can make it here by adding a font name in the line 'font-family'.
.ddimgtooltip {
z-index: 2000;
box-shadow: 3px 3px 5px #818181; /*shadow for CSS3 capable browsers.*/
border-radius: 10px;
display: none;
position: absolute;
border: 1px solid black;
background: white;
color: black;
padding: 0 7px 3px 7px;
font-family: sans-serif;
font-size: 10px;
}
In both cases think of the specification 'sans-serif': You have to use a font that is 'sans-serif', otherwise you have to use 'serif' or leave it away anyway.
Hope this helps.
Cheers,
Reinhard
-
Mark:
I have a repeat of the weird scaling on the Apparent Temp Gauge. See attached screenshot of the gauge and copy of the realtimeguagesWC.txt file. Do you see anything in the txt file that could be causing this?
Odd, I can't see any issue with the data file, I have been visiting your site off and on all day and haven't seen the issue either. I think I'm going to need to catch it happening to diagnose the problem. :(
-
Reinhard:
I almost have it! I have figured out how to change the font for everything except the labels: Inside, Outside, Apparent, etc. and I also cannot yet change the font of the labels in the U o M box: Temperature, Rainfall, Pressure, etc. There are two different places that effect the way the credits display. I can change the size of the radio buttons and the credits at the bottom but not the label items. Still looking...
Thanks for the tip on the popup graph font.
-
Blick:
The font of the labels on the gauges themselves are specified in the 'steelseries.js' file, I *think* (look at this file and find line 35 and line 36) - but I have not touched them on my side. The UoM-Box fonts should be able to be reached by the 'body' settings in css as I mentioned before. When I look at your site you have specified 'body' in the 'gauges-ss.css' with 'Verdana, Helvetica,...' -just change those to lets say 'Courier' to see the affect.
Cheers,
Reinhard
-
Hi Blick,
just want to say that you have done a great description on your live gauges explained site (http://timberlakesutah.com/weather-gauges-explained/). Congrats!
Cheers,
Reinhard
-
I might have to refer people to that page myself - good job.
-
Mark and Reinhard:
I am delighted that both of you took the time to look at the gauges description page on my website. I have both of you to thank for helping me understand what the gauges are displaying. If either of you know something on that description page needs to be corrected to be more accurate, or if something needs to be added or deleted, please do not hesitate to let me know.
Cheers,
-
Randall:
I took a look at your gauges. Looks like you found where to play with the font for the scrolling long forecast. Or at least the font looks good to me.