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

Hi Tom,

Could you add this comment on the discuss list where I moved this post? I think there will be more people there with expertise on this than on our marketing list.



Le 2012-07-28 18:21, Tom Davies a écrit :
Hi :)
Surely programming a macro is less likely to suffer from user-error or user-distraction.

Andrew Pitonyak's guide is linked to from

Regards from
Tom :)

--- On Sat, 28/7/12, Marc Paré<>  wrote:

From: Marc Paré<>
Subject: [libreoffice-marketing] Re: Libo discussion group on LinkedIn
Date: Saturday, 28 July, 2012, 22:30

Hi Kostas,

This would be more appropriate on the "discuss" list. I am sending it to
that list for discussion, and, if it needs it, someone will file a bug
for it. I think it would be better to be more specific with the
description of the problem(s) before adding it to a bug list; the
complaint is just too general.

You could perhaps suggest, to whoever is finding the macro recorder
challenging to use, to joinour discuss list and to join the discussion
here where we concentrate on improving the product.



Le 2012-07-28 14:11, Kostas Mousafiris a écrit :

Hi everyone!
I intercepted the following winging about some LibreOffice feature., in
a LinkedIn discussion group
I am not sure if this is the appropriate list
and I also think that it may well be a known issue,
but I would like to report it all the same, in the hope that something
can be done:

       LO macro recorder.

In LibreOffice, the macro recorder is even worse than in OpenOffice.
Compared with Ms Office, OO's one it is a little hell for "simple
users", but LO's is just impossible.

As a trainer, I had to face my disappointed trainee's after their
company has changed from OO to LO.

Does anyone has an experience or comment about that?

22 days ago
✔ Jan V.
likes this

1 comment

✔ Jan V.

✔ Jan

✔ Jan V.
• I do fully agree - I've been using OO since version 1.0. And have
former been developing in MSO 95,97 and 2000. The Experience of the
API in MSO was a mixture of frustration over incompatibility between
versions and a clear picture of the object model. I think that the
OOo/LO API lacks clarity and the Macro is even worse. "ooo macro
programming by andrew pitonyak" gives, I think, the best
dokumentation. :o)

Marc Paré Supports OpenDocument Formats (ODF) Supports

Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.