Le 19 avr. 04, � 21:37, Ugo Cei a �crit :
...Hey, that's not my fault. CalendarGenerator's was ;-).
It's fixed now, please cross-check.
Sorry, I should have done the change myself, it was...not so complex ;-)
I just did a complete build under 1.3.1, successfully, thanks.
Note that I'm not particularly interested in running under 1.3.1, just had it switched on by chance (after testing another 1.3.1 app) when I saw the CalendarGenerator problem.
-Bertrand
