Cumulus Support

It's working perfectly

Pleased to hear that
One small tip: if you want to run multiple copies of the gadget, e.g. my version and your modified one, at the same time in order to compare output, it is difficult to tell on the Windows Gadgets menu which is which.
What I do is simply to go to the gadget images folder, right click the icon image and hit rotate. Then you can distinguish between the different versions.

(it's 1:30 in the morning, going to bed. Over and out)

On the other hand....while it date format WAS wrong in my win 7 set up....correcting it has NOT changed the realtime.txt file. I rebooted and restarted everything...still wrong format for me.

mikeflight wrote:On the other hand....while it date format WAS wrong in my win 7 set up....correcting it has NOT changed the realtime.txt file. I rebooted and restarted everything...still wrong format for me.

SORRY...didn't even think about your time as the early AM. Get some sleep....it'll all still be here in the morning.

mikeflight wrote:while it date format WAS wrong in my win 7 set up....correcting it has NOT changed the realtime.txt file. I rebooted and restarted everything...still wrong format for me.

The date format in the realtime.txt file is fixed, so that any software reading it knows what format to expect, regardless of the machine settings.

steve wrote:

mikeflight wrote:while it date format WAS wrong in my win 7 set up....correcting it has NOT changed the realtime.txt file. I rebooted and restarted everything...still wrong format for me.

The date format in the realtime.txt file is fixed, so that any software reading it knows what format to expect, regardless of the machine settings.

I was wrong about that. Sorry

In the gadget, it is a 2-line modification to change the date to a US-format.
I have built a version that has an optional settings.ini parm: usdate = '/' where the parm is the separation char. wanted for US-format.
I can upload if there's an interest.....

(Steve: I am uncertain about the separation char. in realtime.txt: Cumulus Help says: always dd/mm/yy.
Your realtime.txt has a slash, but in mine it is a dash )

dane wrote:(Steve: I am uncertain about the separation char. in realtime.txt: Cumulus Help says: always dd/mm/yy.
Your realtime.txt has a slash, but in mine it is a dash )

Yes, I'm afraid this is another one of those things that 'just happened' when people started using Cumulus that I didn't realise was going to happen. Although Cumulus asks for a date in the format "dd/mm/yy" what actually happens is that the slash gets replaced by the PC's date separator symbol. So the correct specification of the format is really: dd<separator>mm<separator>yy.

Yes, I'm afraid this is another one of those things that 'just happened' when people started using Cumulus that I didn't realise was going to happen. Although Cumulus asks for a date in the format "dd/mm/yy" what actually happens is that the slash gets replaced by the PC's date separator symbol. So the correct specification of the format is really: dd<separator>mm<separator>yy.

Thanks. I'll code to handle any separation character.

Gadget code and documentation updated to version 2.1IH.
New: optional settings.ini parameter: usdate = "/" for US date format (mm/dd/yy) in output, using specified separation character.

Download from 1st post of this thread.

dane wrote:Gadget code and documentation updated to version 2.1IH.
New: optional settings.ini parameter: usdate = "/" for US date format (mm/dd/yy) in output, using specified separation character.

Download from 1st post of this thread.

THANK YOU THANK YOU THANK YOU. It's PERFECT

I have just noticed that the Gadget had stopped updating. Data was 9 hours out of date.
It updates locally and both computers have been running all that time.
Clicked on options and then "OK" and it now updates again.
Seems to just go to sleep.

Super-T wrote:I have just noticed that the Gadget had stopped updating. Data was 9 hours out of date.
It updates locally and both computers have been running all that time.
Clicked on options and then "OK" and it now updates again.
Seems to just go to sleep.

I am aware of the problem, but have no fix for it.
The code does an Open of the local file - but the system never returns.
This is a local-file problem - does not occur for website files accessed via http.

Update 2010-07-16: (version not changed: still called version 2.1IH):
- modified code to handle local realtime.txt. New code uploaded to the first post of this thread.
Maybe - just maybe - the local realtime.txt problem has been fixed now

I'll give it a bash and see how it goes

The Cumulus Realtime Gadget is giving problems regularly when run from the realtime.txt on my local network. It stops updating and I have to go to Options and click ok, without changing anything, and it then updates and carries on. Settings are r:\realtime.txt - a mapped drive.
I should add that the computer that is running the gadget is put into "sleep" mode overnight but this does not always give a problem. Drive is still mapped but the gadget doesn't update.
Any ideas?

Super-T wrote:The Cumulus Realtime Gadget is giving problems regularly when run from the realtime.txt on my local network. It stops updating and I have to go to Options and click ok, without changing anything, and it then updates and carries on. Settings are r:\realtime.txt - a mapped drive.
I should add that the computer that is running the gadget is put into "sleep" mode overnight but this does not always give a problem. Drive is still mapped but the gadget doesn't update.
Any ideas?

I am aware of the fact that the gadget will tend to stop working if the realtime.txt is on your local system.
And I have given up trying to fix the problem: the gadget simply hangs with no error indication.
After all: the gadget works fine as intended: against a realtime.txt on a website.
My attempt to recode it to run against a local realtime.txt was only an experiment - and it failed.