A test entry 'TEST' produced a calendar.cld with a long line of numbers. At the end of this line I can find the 'TEST' entry.
That's correct.
- The first 100 bytes are year header offsets for 10 years (10 * (4 bytes year + 6 bytes offset)).
- The next 96 bytes are month offsets for the first year (12 * (2 bytes month + 6 bytes offset)).
- The next 248 bytes are the day offsets (31 * (2 bytes day + 6 bytes offset)).
- The next 192 bytes are the hour offsets (24 * (2 bytes hour + 6 bytes offset)).
- The last 60 bytes are the entry ('TEST\0'+55*' ').
All unused offsets are 000000. If you add a new entry it search for the needed year header then the needed month header and so on to the hour/entry. If any of the needed headers aren't available it creates the needed headers / entry at the end of the file and sets the offsets to the needed values (end of file).
The CHDK calendar displays the first numbers of this line (60 chars?).
No, it displays the entry (see above, with only one entry the last 60 bytes of the file).
When I scroll down to the next hour entries (I've made the test at '00'.) the line at '00' will be not completely erased.
That's an error and I will try to fix it (i wonted anyway rewrite the draw functions for that part).
Some days ago in German forum we had a discussion about sunset/sunrise data for all. genie01 had made a CHDK version for displaying astronomic data based on GPS. So the mathematical basics are available.
I've read that, but my camera hasn't started with that version, so I couldn't test it.
Non GPS cameras need coordinates for the calculation of sunset/sunrise data. We could use the text box or a text file for the coordinates.
I've made a number box for this purpose (look
here).
The sunrise and sunset times in the calendar view would be a very good improvement.
That's a good idea, I hope we can combine this.
TobiMarg