Since I upgraded LibreOffice to version 4.3 (on MacOS X, 10.8.5) TexMaths does no longer work. I only installed v. 0.39 in August or so (for the first time, and it worked nicely with the older LibreOffice version), and hence I was clear that this has to do with the version change of LibreOffice.
Today I now tried version 0.41 to see whether it works, but same issue: I get the following error:
BASIC runtime error. Object variable not set.
and the macro editor pops up and shows me this statement:
oDrawDocCtrl = oDrawDoc.getCurrentController()
in TexMathsTools, line 428
Since I have no clue about macro programming in LibreOffice (but know LaTeX/pdfLaTeX) quite well, I cannot solve such an issue myself. Any ideas how to set that object variable?
Try remove "~/.config/libreoffice" directory.
This worked in my Slackware.
Hi Rudson
thanks for the suggestion. Although I am not using Linux, it helped me to find and solve the issue on my Mac. Here is what I found out:
there is no ~/.config/libreoffice directory, but it works if I remove the following directory from my Mac:
~/Library/Application Support/LibreOffice/4/user
since this also removes all my settings, I tried to find out what makes the difference between a "clean" new installation and what I had, and it seems to be one single file:
~/Library/Application Support/LibreOffice/4/user/TexMaths/tmp/.~lock.tmpfile_.svg#
If one removes this file it works again. My best guess is that this lock file was remaining from a LibreOffice crash and it may just be a coincidence that I used TexMath before upgrading to version 4. In any case: if other Mac users have the same issue, then executing this command should solve the issue:
cd $HOME//Library/Application\ Support/LibreOffice/4/user/TexMaths/tmp
rm .~lock*
(or similary).
Thank you very much for your support!
Best,
Werner
Werner Eugster
Grundrebenstrasse 109
8932 Mettmenstetten
T 043 466 81 49
E werner.eugster@gmx.ch
On 26 Oct 2014, at 19:27 , "Rudson Alves" alves67@users.sf.net wrote:
Related
Bugs:
#50Thanks for investigating further ! A simple
fixed it, indeed (On openSUSE 13.2).