Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
Yet another update for the Alternative Interface - apologies for the number of updates released.
This update addresses the following issues:
The Dew Point (Other Temperatures) gauge was not showing the Feels Like values. This was due to me omitting them from the gaugefeed.js file!
The title for the 'Dew Point' gauge now also reads as 'Other Temperatures' which is more accurate.
The popup editors used on the log pages were not showing labels - they were but they were the same colour as the background. The AltEditor.js library file has now been included in the package as I have edited it to use the w3Pro styles. (Please note that I have done just enough to make this work in this situation and it may not show error messages if it ever did).
AI CumulusMX Latest.zip
The zip package includes a pdf file explaining what I have done and how to install / use it.
You do not have the required permissions to view the files attached to this post.
Neil Thomas
website: oaktreewebs.co.uk | Davis Vantage Pro II | CumulusMX, Raspberry Pi 4 | MX V4 build 4019
I have just downloaded the latest version and note that the hover over the gauges looks good.
The other temps gauge works but when it starts up it shows a dewpoint value that is the feelslike value. However if you reselect another value ie wind chill and then go back to the dewpoint value it shows the same value as in the CMX desktop. This was after clearing the cache on my browser just to ensure I was not looking at old data.
Not sure what is going on in the background but something seems slightly off.
I tend to like dark backgrounds to most things, as brighter ones hurt my eyes.
How hard would it be to implement dark backgrounds (not pure black) for all of the current themes? For example, have a drop down menu next to the themes menu to select light/dark?
I am now looking at the next developments for the Interface. The ideas I have at the moment are:
Including any Davis station information on the dashboard. Only of real interest to this of you who use Davis weather stations. I want to display Packet and error log data so that I can see if there are any communication problems or if the battery is getting low.
I also want to display new record flags. At the moment I am looking to just put the four main categories on the dashboard as I think it might get a little overcrowded to include all possible variations.
The alternative to including it all on the Dashboard would be to do another page showing the dashboard data in a tabular layout and including every possible record on that.
Screenshot Dashboard.png
The image shows my v3 dashboard page partially complete. Any observations welcome.
You do not have the required permissions to view the files attached to this post.
Neil Thomas
website: oaktreewebs.co.uk | Davis Vantage Pro II | CumulusMX, Raspberry Pi 4 | MX V4 build 4019
Noted that all four of the 'Edit Records' pages were not displaying the 'Loading' panel. This has now been corrected and more theme colours added to the popup edit box.
The only files that have changed are to do with editing records; all-time, monthly, this month and this year. See below for details.
alltimerecseditor.html, monthlyrecseditor.html, thismonthrecseditor.html and thisyearrecseditor.html
All these have had the x-editable.css stylesheet correctly referenced - the 'x' should be 'X'. I have also adjusted the panel at the bottom of each page to be correctly structured. This means that only the main div has to be shown/hidden. See below.
The associated js files for the above pages have been modified to only hide/show the main 'loading-overlay' panel.
The X-editable.css stylesheet has been modified to include theme colours in the popup edit window and make all child elements of the loading-overlay visible.
Changes made to the loading overlays at the bottom of every affected page:
I'm still seeing this issue with the gauges page where the temp/dewpoint gauge continually refreshes. It only does this on the alternative dashboard, the regular dashboard works fine. Any ideas?
gauges.gif
Thank you
You do not have the required permissions to view the files attached to this post.
Not seeing this on my system. I'll take a look and see if I can duplicate the effect and get back to you.
Neil
If you need anything specific to help you with this, just let me know. I'm a software QA Engineer by trade so I'm sure I can help with whatever you need. Thank you.
I am not seeing this either. Sorry to ask but have you deleted the contents ai.cmx folder and copied all the new release in, as that is what I did and it is working perfectly. Might be worth also clearing your browser cache as sometimes the wrong version is kept by the browser even though have updated the the folder.
I tried it using the the newer version and put in a different folder than the first version. Both versions exhibit this and I'm not sure why. I'll likely remove both folders and then download fresh and the put where it should go.
@BigOkie,
I have seen that constant refreshing a while back on another 3rd party template, that uses the SS gauges as well, with which I was helping a user. It was occurring on the other user's site but mine was ok. Best I can recall is that an update to latest version fixed it.
PaulMy wrote: ↑Fri 03 Dec 2021 4:16 pm
@BigOkie,
I have seen that constant refreshing a while back on another 3rd party template, that uses the SS gauges as well, with which I was helping a user. It was occurring on the other user's site but mine was ok. Best I can recall is that an update to latest version fixed it.
Enjoy,
Paul
OK,
Pulled the old versions of the interface (still had v1, put the initial v2 up). Previously, I had just unzipped the file and transferred the individual files over. This time I transferred the zip file and unzipped it on the target machine. I'm not sure what it was, but that did the trick. The gauges work fine now.