BarryG wrote:I was hoping this Date64 module would be a direct drop-in replacement for the native Date commands without me changing anything in my source code
It doesn't work that easy. The macros replace the native date functions of PB, but if the variables that receive the return values of the new Date64 functions are not of type
Quad, then the programmer has to adapt this in his code himself. In addition, the macros only work in the main code. If date functions are also used in modules, they are not replaced there. To do this, the macros have to be inserted additionally inside each module at the beginning.
BarryG wrote:but it causes macro errors if your variable names contain the macro keywords.
That's one reason why variables shouldn't preferably have the same name as functions. I improved the macros in my previous post.
BarryG wrote:Also, the Date64 module doesn't work with the CalendarGadget. Try the below, then click January 20 (or any later date) and it fails. Can it be made to work with CalendarGadget (and I guess the DateGadget too)?
The Date64 module does not currently provide a 64 version of the
SetGadgetState() and
GetGadgetState() functions. This is on my ToDo list (in the best case for all OS). I saw that you got an alternative solution code in the other forum thread. Maybe this is enough for you.