Superb, Nod5! Thank you so much!!
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Just a reminder to everyone that if you want to encourage the coders on the site, you can make a donation to them by clicking the gold coin under their name.-mouser (August 16, 2017, 01:15 PM)
@orbis: Uploaded a new version with corrected timing.-skrommel (August 16, 2017, 12:55 PM)
but it has the unfortunate side-effect of making the chime and voice sound every second for the minute it's set to run.-orbis (August 14, 2017, 09:37 AM)
Ah, apologies for that. I didn't look too closely at the source.Might there be a way round this?-orbis (August 14, 2017, 09:37 AM)
To answer your question, yes, it'll take further code modifications to do what you want. Unfortunately, I do not have time today to look at the source more closely (regular job getting in the way ). If Skrommel doesn't get to it first, I'll try to find time later this week.-skwire (August 14, 2017, 10:01 AM)
Thanks. I'd certainly sacrifice some CPU for a bit more accuracy here.
Or is there a setting which users can change, perhaps?-orbis (August 14, 2017, 06:10 AM)
The source code doesn't have this as a user-definable setting but, if you have AutoHotkey installed, and are using the .ahk file instead of the .exe, you can easily modify the source on line 189 to do what you want.Code: Autohotkey [Select]
The 60000 is 60000 milliseconds, or, 60 seconds. If you want it checking every second, close the script, change the 60000 to 1000, and relaunch the script. Make sense?-skwire (August 14, 2017, 08:52 AM)
@orbis: I use a timer set to 60 seconds, so it can be off by almost a minute. It's just to be as easy on the CPU as possible, but I can easily change it.-skrommel (August 13, 2017, 12:09 PM)