Oh dear! So let me get this straight. Old macros might not work with newer versions of LO.
I realize that backward compatibility leads to "bloat" when carried to the extreme but shouldn't the older specification be deprecated but still supported through two major versions (e.g. version 3.x specification deprecated through version 5.x) or maybe for two years? And shouldn't there be a stand alone migration tool? And shouldn't a library of these tools be available online indefinitely? -- Jim Cley Faye <[email protected]> wrote on Fri, 28 Mar 2014 at 6:45 > 2014-03-28 13:34 GMT+01:00 Marion & Noel Lodge <[email protected]>: > My macro is expecting a single value, but under v4.1 it has three values, > so it's obvious why it is throwing the error. > > In both cases I have used the Java version 1.6.0_29, so I cannot work out > why there is this difference in the way the OdateModel object is storing > its Current Value. I could test for the Current Value's Type each time and > extract the date with appropriate code. But this doesn't seem to be the > right way to go. And there could be other variances between the LO > versions that I haven't come across yet. > > I am running an H2 Database on Windows 7 64 bit. Can anyone spot what I > might be doing wrong with my Java settings in LO v4.1? > There was a change in date objects: <https://wiki.documentfoundation.org/ReleaseNotes/4.1> (look for "Changes to UNO APIs") This looks like the culprit in your case. The best course of action is likely to update your code to follow these changes (either a quick fix to "reproduce" the old value, or more long-term fix in the code around it). -- To unsubscribe e-mail to: [email protected] Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
