Aqua-Soft ForumsWas that the download from the first post? Duckie said it wasn't finished and left it for someone to continue working on it.
A few posts later, judge posted a finished version. Download that one. It uses DuckiesCal.ini which links to DuckieCal.vbs
[help] Sysstats Calendar
Originally posted by mimeryme@Aug 6 2004, 09:38 AMWas that the download from the first post? Duckie said it wasn't finished and left it for someone to continue working on it.
A few posts later, judge posted a finished version. Download that one. It uses DuckiesCal.ini which links to DuckieCal.vbs
<{POST_SNAPBACK}>
Ah-haa... thanks! I should read the posts more carefully... 
But sadly it didn't completely fix the problem ... When using DuckiesCal.ini (and DuckieCal.vbs) the calendar *works* but at the start the debugger window pops up 2 times:
1. Row 7: Set oldDate = DateSerial(1900, 1, 1)
Error: Microsoft VBScript runtime error: Object required: 'DateSerial(...)'
2. Row 33: weekdays(i-1).Format = i-firstDay+1
Error: Microsoft VBScript runtime error: Type mismatch: 'weekdays'
So I can actually use the calendar but it's quite annoying to close the "Just-In-Time Debugging" window twice everytime I restart my computer 
Originally posted by Cerebral@Aug 3 2004, 06:55 PMAs far back as I can remember, that's how calendars have been laid out:
Sun Mon Tues Wed Thurs Fri Sat
<{POST_SNAPBACK}>
Not in Finland 
Originally posted by tomi@Aug 6 2004, 10:11 AMSo I can actually use the calendar but it's quite annoying to close the "Just-In-Time Debugging" window twice everytime I restart my computer
<{POST_SNAPBACK}>
Ok... found the solution... it was almost too easy :smartass:
I disabled the Just-In-Time debugging for scripts from Visual Studio .NET. No annoying debug windows anymore 
Originally posted by LoofyGun@Aug 6 2004, 08:59 AMNot in Finland
<{POST_SNAPBACK}>
There should be an alternative config for Mondays as the first day of the week. I'll see if I can figure out something.
On the topic of configs, I noticed that there were 60 d/ls for the modified config I attached. I assume all is well w/ the config/script. I wondered though as I had modified judge's original script when I was changing months and noticed a discrepancy with the marker placement.
Originally posted by k21975@Sep 8 2004, 10:45 PMMimeryme,
Will your fixed script work w/ the regular sized calendar?
Thanks.
<{POST_SNAPBACK}>
Hmm, I think the values were changed to fit the smaller calendar space. I'll take a look at it and hopefully can post it soon.
edit: Ah, it was 3 lines that affected most of the script. Here's the original script modified for the original calendar. marker.X and marker.Y (lines 48-49) as well as the If DateIff(...) > 0 (line 15). On line 15, > was changed for <> as I was testing the script. W/o this change, applying new dates can be problematic as once you set a new later date, the script won't go back should you set an earlier date.
edit2: This is for LoofyGun and others who start their calendar week on Monday. It was a one parameter change (vbSunday to vbMonday). So easy. Sorry, I didn't take a look at it sooner. (I included the config file w/ the changed weekday/end heading, but I didn't put them in folders, so you have to put it in config and scripts yourself.)
Thanks! When I first loaded the new script, it said it was Sep. 2nd and the marker was on the 2nd as well. I finally got it right when I opened my computers internal time/date and changed the date to something else and then set it back to the 9th again.
Also, I noticed (not that this would ever happen) if I set the date using the system time/date to a date more than 4-5 days ahead of the current set date, then the marker was off again from the highlighted number.
But it working now! I let you know next month if it's still working!
Thanks again.
---Update----
I tried setting the date to Sep. 30th and then changing the date to Oct. 1st. and the same marker off set happend. The Marker started on the first possible location (ie. a blank Sunday) and the highlighted date was the 1st which was a Friday. I could fix it by choosing something like the 20th of Oct. and then go back to the 1st.
Hope this info helps.
k21975, did you have the calendar loaded already before you tried the script? I believe you would need to delete the instance of DuckieCal, replace the script, restart AveDesk and then reload SysStats with DuckieCal config.
I did try what you tried in your updated post and the results on my end are correct.
@others, can you try the steps k21975 described above and report your results.
It works much better now. I deleted Duckie Cal and then replaced the script. Then I loaded a new instance of Duckie Cal and saved my settings. Everything works just Duckie now.
(I like the work Duckie because it's my Dog's name, and no it doesn't have any thing to to with "The Real Duckie". My wife named her that two years ago.)
Next questions. I am working on a aero-glass version for everyone over at Aero-Soft. (I guess I'm also asking for permision to release it from Duckie and mimeryme, if I can get it to work right) I need to shift all of the text down and to the right 5-10 pixels so I can have the 'glass' border. Is there any quick and easy change in the config or script that I can change to make this happen? Or do I need to change the parameter for each overlay like I've started to do?
Thanks for the help.
You needn't change the individual days' overlays' X and Y values,. The first four lines in the script determine spacing and where the marker needs to be. If you want to change the positioning of the days, modify the value for the 'Weekdays' CompositeOverlay (which has all the days' overlays in it).
When changing the script around, you need to unload the config and reload it and I believe it is safer if you also exit AveDesk as the script may still reside in memory otherwise.
Originally posted by judge@Sep 9 2004, 12:26 PMFor many script change you can just reload the script. If you're loading a new script it you 'just' need to delete and re-add the desklet.
<{POST_SNAPBACK}>
Ah thanks for the correction judge.