Niklas Nebel wrote: > Mathias Bauer wrote: >> The whole magic behind that is that 01-01-1601 is taken as an invalid >> date. I don't know why this date was chosen but perhaps somebody else >> can shed some light on this. > > January 1, 1601 is the base of Windows file time, as used in OLE > SummaryInformation.
Ah, thanks. That's the good thing in being on a mailing list. You can learn something new every day. :-) So it makes sense to use this define when importing OLE SummaryInformation. The question remains how we should handle this in the rest of the code. We could either use the same approach for css.util.DateTime also but then we should document it in the IDL file. Or we should remove the define for an invalid timestamp and instead use a static IsInvalid() function that checks for both values (the OLE one as well as the "void" case for css.util.DateTime). I don't believe that using a TimeStamp with nDate=0L (that's what we get when we convert a "void" css.util.Datew to a "tools" Date) can be anything else than an invalid Date. I would prefer the second way as using gthe Windows file time in our IDL looks a bit strange. In case noone objects I will create an issue to change this as described. Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "[EMAIL PROTECTED]". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
