https://bugs.freedesktop.org/show_bug.cgi?id=68751
--- Comment #9 from Lionel Elie Mamane <[email protected]> --- (In reply to comment #8) > This just cost me two or three [profanity resisted] hours. Please document > changes that will break code in a prominent and appropriate place Like https://wiki.documentfoundation.org/ReleaseNotes/4.1#Changes_to_UNO_APIs ? > (this change is not mentioned in the API reference at > http://api.libreoffice.org/docs/common/ref/com/sun/star/awt/XDateField.html). It is mentioned in the API reference of the SDK version 4.1.1. Downloadable from the same place as LibreOffice itself, i.e. your distribution's package repository or http://www.libreoffice.org/download/ (click "Software development kit (SDK)"). The on-line one apparently is from an older version... Good point. I'm going to find out how to get it updated. > And would it have been *so* much extra work to provide CDateToDateStruct and > CDateFromDateStruct functions? Not sure what you mean. Amount of work depends on what they are supposed to do, where they are supposed to be available (Java, Python, Basic, all of them, ...), ... From the name "CDateToDateStruct" my guess is that you expect them to convert from a C Date to a UNO Date; except that I don't know of a standard C date type, so maybe you mean the OS-specific type? E.g. "struct tm" on Unix? LibreOffice uses such functions internally in its C++ code, so we could consider exporting them in the SDK for C/C++ extensions to use... Is that what you mean? -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
