[libreoffice-users] Re: LO Basic: DialogLibraries contains no elements

Hi Paul, Paul D. Mirowsky wrote > Check spelling. thanks for your hint, but we already checked that. The problem is that the "ElementNames" list inside DialogLibraries contains nothing, not even "OOoLilyPond" in a different spelling. Still hoping for a good Idea... -- Sent from:

[libreoffice-users] LO Basic: DialogLibraries contains no elements

Dear LibreOffice community, I have an extension "OOoLilyPond" written in LO Basic: https://extensions.libreoffice.org/extensions/ooolilypond For many users (including myself) it works without problems. However, some users have

[libreoffice-users] Re: LibreOffice Basic macro stops working after upgrade from LO 6.0 to LO 6.1

Hi Alex, Alex Thurgood wrote > Look for a message with the following title on the dev mailing list : > > API-CHANGE - dropping string properties which use > vnd.sun.star.GraphicObject URL Thanks for your info. After lots of reading, now I know that I used a deprecated way of loading image

[libreoffice-users] Re: LibreOffice Basic macro stops working after upgrade from LO 6.0 to LO 6.1

Hi Robert, thanks a lot for your examinations. Robert Großkopf wrote > ... but you will create a string of this. This coudn't work. What do you > wan't to get from the object? You are right, it's only the beginning of the function. I tried to strip it down to a minimal example. The string

[libreoffice-users] Re: LibreOffice Basic macro stops working after upgrade from LO 6.0 to LO 6.1

Hi Robert, thanks for your reply. I have formatted all code snippets as "raw". In the preview, they were still there, but here it seems that nabble has completely removed them. This time, I'll work without formatting. Okay, here is my question again: I have a macro that loads a svg image

[libreoffice-users] LibreOffice Basic macro stops working after upgrade from LO 6.0 to LO 6.1

Hi, I have a macro that loads a svg image file and inserts it into a Writer document: In earlier LO versions up to 6.0.6.2 this works without problems. Now I have upgraded to 6.0.1.3 and the line causes the following error: OS is Windows 7 (64bit). I have no idea what is