Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


On 04/03/2013 at 07:54, "M. Fioretti" <mfioretti@nexaima.net> wrote:

Greetings,

the subject says it all. I have already searched online, and am
looking at the manual but apparently (maybe I used the wrong terms) it
is not easy to find CURRENT information on macro compatibility between
LO 4 and AOO 3.4.1: will all macros created in one tool also work in
the other?

If not, why and when? What are the reasons/cases when a macro is not
portable?

It depend on LO version. Any existing macro working in latest AOO should also 
work in LO 3.6 and earlier. LO 4.0 has some changes in API that may render 
macros (and extensions) unusable, depending if they rely on changed parts of 
API or not.

For excessive list of changes take a look at release notes of 4.0:
<https://wiki.documentfoundation.org/ReleaseNotes/4.0#API_Changes>
The same may go to 4.1, 4.2 etc. Any changes in API will be noted on release 
notes wiki page, so take a look there if in doubt.
-- 
Best regards
Mirosław Zalewski

-- 
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
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

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.