Hi.
It seems it works now. I did a fresh installation of LibO 4.0.4, like I had
done before, but this time I made sure I erased all the remaining files both in
Windows "Program Files" folder and in the users' "AppData" folders (these are
usually hidden). Now, these folders (particularly the AppData ones) remain with
some information about the users' preferences, and are not erased during the
uninstallation process (in case one wants to reinstall LibO later, I guess).
Among this information there are some XML files and other stuff related to the
extension preferences.
As the problem started with the upgrade to LibO 4.1.0, my guess is that
probably some of those files were modified during the upgrade, and something
went wrong. Then, when I found out that the extension was not running and
downgrade to 4.0.4, the configuration files remained untouched, so 4.0 couldn't
find the missing paths either.
I also tried to install other extensions before fixing the problem, and they
actually gave me the same problem: they could not find the dialog macros. The
pattern was always the same: if I installed the extension and did NOT close
LibO, the extension ran. Once I closed LibO and I restarted it, the dialog
macros would be missing. So, most likely LibO reads those user configuration
files when it starts, and therefore all the erasing or changing of the macros
is done at this point.
Configuration files erased, I checked this pattern (install the extension, run
it without restarting LibO, restart LibO, run the extension again) several
times, and found no problem at all.
Now, if this happened because of the upgrade and / or the downgrade, will
probably give trouble to other people and, maybe, is a symptom something should
be checked during the installation and uninstallation processes so the
configuration files that remain from previous versions are properly handled and
compatibility problems can be avoided.
I'm an absolute layman in programming, so I write this here with the hope it
will be useful to the people really working on the project. Maybe someone could
systematize this info and create a bug report or something if they think it
necessary.
So thanks everybody. Regards,
Joaquín
________________________________
Hi
To bad it did not work out for you. I can't see any issue with the way
you installed as a shared extension. I usually start LibreOffice as
administrator and install the extension through the GUI instead of doing
it the terminal way but that is just a preference.
Med vänlig hälsning
Niklas Johansson
Joaquín Lameiro skrev 2013-08-12 17:25:
> Hi. Thanks for the help, Niklas.
>
> First: Neither DlgAbout nor DlgBookmark under eLAIX node when installed as a
> user extension.
>
> Second: I followed your advise and try to install eLAIX as a shared macro,
> but it didn't work either. I just summarize what I did so you can check I
> didn't make any mistake:
>
> I'm running LibO 4.0 on Windows Vista 32 bits SP 2. I opened the extension
> manager through the GUI (Tools -> Extension manager) and uninstalled eLAIX. I
> closed LibO and downloaded the OXT file from the web into my user folder. I
> right-clicked on the Windows promt icon and selected 'Open as administrator'.
> The Windows prompt popped up in a new window. I executed 'unopkg add --shared
> c:/path/file.oxt' from the 'program' sub-folder of LibO (of course I changed
> the 'path' and 'file' generic names for the actual ones). Unopkg run without
> problems, printed a copy of the license and asked me to agree, which I did.
> It came out to the promt without error. I exited the administrator promt and
> started Write. The eLAIX extension was installed, but:
> -gave the same error
> -when checking the macros manager (Alt+F11), eLAIX was under the shared
> macros, but DlgAbout and/or DlgBookmark were still missing from the node.
>
> No idea why the macros are being deleted, but hope this information could
> help to report a bug (I don't have the knowledge to report it properly).
> Thanks again everybody,
> Joaquín
>
>
>
>
> Sorry to hear that you are still having troubles with this.
>
> So what that line of code is suppose to do is to load the dialogs in the
> library eLAIX so that they can be used by the program. For some reason
> this is not possible.
>
> I've seen some problems with dialog libraries disappearing in some cases
> so let's see if we can pin down if this is what has happened.
>
> Open Writer
> Press Alt+F11
> Press the button Edit in the dialog that appears
> On the left side in the editor you have a tree structure, find eLAIX and
> expand that node
> Do you see a DlgAbout or DlgBookmark there under?
>
> We should probably try to formulate a bug report about vanishing dialog
> libraries (as well as basic libraries). I found it hard to formulate
> such a bug since I haven't found when it happens just that it happens
> some times, and I believe it's more and more frequent.
>
> Just a thought, you could try to install the extension as a shared
> extension.
> If it is installed as a shared extension then LibreOffice will need
> elevated rights to change the dialogs, which it should not have under
> normal circumstances. Of course this does not fix the actual problem but
> it might make it possible for you to use eLAIX without having to
> repeatedly reinstalling the extension each time the dialogs disappear.
>
> Let us know if you need more information on how to install a shared
> extension, and in that case please let us know what operating system
> your using (Windows, Mac, some sort of Linux distribution ...)
>
> Regards,
> Niklas Johansson
>
> Joaquín Lameiro skrev 2013-08-12 13:56:
>> Hi.
>> Seems it was not that easy to solve. The reinstallation of eLAIX worked the
>> first time, but now I'm getting the same problem again. Besides the error
>> message, LibO opens the Basic editor and outputs the macro, marking the line
>> that is causing the problem. I copy the pertinent part of the output, and
>> underline the specific line, which is actually 'DialogLibraries.LoadLibrary(
>> "eLAIX" )' from the "Document related functions" section:
>>
>>
>> [...]
>>
>> '******************************************************************************************
>> ' Document related functions: Doc Open | Doc Metadata | Doc Check | Doc
>> Export
>> '******************************************************************************************
>>
>>
>> function DocImport()
>> ImportFromILIAS
>> end
>> function
>>
>>
>> sub DocCheck()
>> dim oGraphic as object
>> dim oControl as object
>> dim sPath as string
>> dim sImgPath as string
>> dim oStructure as object
>> dim oSyncOutlines as object
>> dim oEmptyHeadings as object
>> dim oDoubleSpaces as object
>> dim oStatus as object
>> dim vState as integer
>>
>>
>> 'initialize dialog and elements
>> DialogLibraries.LoadLibrary( "eLAIX" )
>> goDlgCheck = CreateUnoDialog( DialogLibraries.eLAIX.DlgCheck )
>> sPath = GetPackageDirURL("vnd.harryboldt.elaix")
>> sImgPath = sPath & "/icons/dialog/check.png"
>> oControl = goDlgCheck.getControl("imgLogo")
>>
>> oControl.getModel().ImageURL = ConvertToURL( sImgPath )
>>
>> 'setting the dialog elements
>> oStructure = goDlgCheck.getControl("chkStructure")
>> oSyncOutlines = goDlgCheck.getControl("chkSyncOutlines")
>> oEmptyHeadings = goDlgCheck.getControl("chkEmptyHeadings")
>> oDoubleSpaces = goDlgCheck.getControl("chkDoubleSpaces")
>> oStatus = goDlgCheck.getControl("txtStatus")
>> oStatus.Text = "Please select check-options and then start the
>>document check and optimizing."
>>
>> 'get check-setting from document
>> oStructure.State = GetInternalDocString("eLAIXCheckStructure")
>> oSyncOutlines.State = GetInternalDocString("eLAIXCheckSyncOutlines")
>> oEmptyHeadings.State =
>> GetInternalDocString("eLAIXCheckEmptyHeadings")
>> oDoubleSpaces.State = GetInternalDocString("eLAIXCheckDoubleSpaces")
>>
>> goDlgCheck.execute
>> end sub
>>
>> [...]
>>
>>
>> ________________________________
>>
>> Hi :)
>>
>> Congrats on fixing it! Sometimes it is worth pinpointing exactly what
>> caused the problem but other times it is better to shrug it off and put it
>> down to bad luck which you have now beaten (inshalla). Maybe if it happens
>> again it might be worth
>> finding the cause?
>>
>> Regards from
>> Tom :)
>>
>>
>>
>>
>>
>>
>>> ________________________________
>>>
>>> Thanks, Niklas and Fernand.
>>>
>>> I just reinstalled once more eLAIX 4.0.3 and now it runs perfectly. Anyway,
>>> before reinstalling it, I check the BASIC macros and LibO had eLAIX there
>>> (under "My macros"), but, apparently, some of the paths were wrong. Maybe
>>> because I first installed eLAIX on LibO 4.1 and then downgrade to 4.0? No
>>> idea, but still it works now, so thanks everybody!
>>>
>>>
>>> Joaquín
>>>
>>>
>>> ________________________________
>>>
>>> Hi Joaquín
>>>
>>> It sounds like the macro code is not located where the toolbar thinks
>>> it's located or is missing.
>>>
>>> If you press Alt+F11
>>> Under My macros (Mina makron in Swedish) do you find a eLAIX?
>>> if not do you see eLAIX under LibreOffice Macros
>> (LibreOffice-makron)?
>>> I did personally not have any issues installing and using the extension
>>> on LibreOffice 4.0.4 on Windows 7 64-bit so it should be compatible with
>>> that version.
>>>
>>> Just to make sure, you have reinstalled the extension, in any case do it
>>> again and see if you get any different result. Something might have gone
>>> wrong when you upgraded that might be fixed by uninstalling and
>>> reinstalling the extension.
>>>
>>> Med vänlig hälsning
>>> Niklas Johansson
>>>
>>> Joaquín Lameiro skrev 2013-08-08 14:26:
>>>> Hello.
>>>>
>>>> I have installed the eLAIX extension for Libre Office and it won't work.
>>>> No matter what action I try to perform, I get a message of this kind:
>>>> "BASIC runtime error.
>>>> An exception of
>>>> Type: com.sun.star.container.NoSuchElementException
>>>> Message:
>> occurred."
>>>> (the message occurs in Swedish, this is a quick translation).
>>>>
>>>> I used eLAIX for Libre Office in other computers and systems, and it
>>>> worked perfectly, so I have no idea what the problem might be.
>>>> This time, I am running Libre Office 4.0.4.2 on Windows Vista 32 bits SP 2
>>>> and I've tried eLAIX versions 4.0.3 (current stable version) and 4.0.1
>>>> (first version supporting LibO 4.0). I had previously tried eLAIX 4.0.3 on
>>>> LibO 4.1.0, and I thought the problem was due to eLAIX not supporting LibO
>>>> 4.1, so I uninstalled LibO 4.1 and returned to 4.0. Anyway, the problem
>>>> still the same: no matter what version of LibO or eLAIX I use, I get the
>>>> above error message or something similar.
>>>>
>>>> Could you give me a hand on this? Thanks for your kindness.
>>>>
>>>> Best regards,
>>>> Joaquín
>>>>
>>> --
>>> 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
>>> --
>>> 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
>>>
>>>
>>>
>
--
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
--
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
