I'm trying to update some Windows VBS code that I wrote a while ago, which uses OO.org or LibreOffice to convert WordPerfect files into DOC or RTF format. Until recent versions of LibreOffice were released, the script worked as it was designed - meaning that it converted the file, using OO.org or LibreOffice to run invisibly. With the current version of LibreOffice, LibreOffice appears when the script runs. The line in my code that makes LibreOffice visible is this: CODE: SELECT ALL EXPAND VIEW Set OpenOffice = CreateObject("com.sun.star.ServiceManager") According to a report here, the same problem occurs with Delphi: http://user.services.openoffice.org/en/forum/viewtopic.php?f=45&t=43872#p211339 My VBS code is a standalone VBS file. If anyone cares to see what happens, the code is here: http://dl.dropbox.com/u/271144/wp-ood.vbs And a description of it is here: http://www.columbia.edu/~em36/wpdos/converterscripts.html#openscript If there is any way around this problem, or if it's a genuine bug, I'll be grateful for any information.
@em36: The first LibO version in what you saw the problem is?
I wish I knew which version first showed it. I believe 3.3, but there was a long period in which I did not test the VBS script, so it could have been earlier. Apologies for not being more exact about it.
weird windows specific bug, perhaps mmeeks' headless refactoring broke it, probably only Noel knows this obscure basic stuff... reporter claims it's a regression.
(In reply to comment #3) > weird windows specific bug, perhaps mmeeks' headless refactoring broke it, > probably only Noel knows this obscure basic stuff... > reporter claims it's a regression. well not really basic related but more to do with ole support :-) I will see if I can reproduce this, ideally the version where it changed would be good, ultimately I suspect that having a side by side comparison of working/non-working might be the only way for a poor windows incapable soul such as myself might figure out what is happening. It's also possible the previous behaviour is just wrong and somehow got unintentionally fixed ( I really don't know ) I suppose we'll find out when we get to the bottom of it. I'll take this bug for now ( but have a couple of days fto so will look at it when I get back )
(In reply to comment #4) > (In reply to comment #3) > > weird windows specific bug, perhaps mmeeks' headless refactoring broke it, > > probably only Noel knows this obscure basic stuff... > > reporter claims it's a regression. > well not really basic related but more to do with ole support :-) I will see if > I can reproduce this ok, thinking about this I would nearly bet that this is no bug at all. Set OpenOffice = CreateObject("com.sun.star.ServiceManager") actually is executed by windows OLE infrastructure which queries the registry finds the GUID associated with the service name above, then searches the registry for the exe ( and associated params ) associated with the GUID ( or something like that ) to launch the office process. I don't think that the params passed to the exe have changed and I don't that the office process should be started 'invisible'. Instead I would bet ( but I cannot check right now ) that we have changed the default for the quickstarter ( see Tools | Options | Libreoffice | Memory | LibreOffice Quickstarter ) to be *off*. Could you check that ? and.. if the quickstarter is not enabled enable it, start libreoffice, exit it and make sure the libreoffice icon is in the system tray ( indicating the quickstarter is active and loaded ) before retesting. Let us know if that helps
I can confirm (Visual Basic 6 code) that with the quickstarter enabled LibreOffice runs invisibly. Thanks for the hint. Bug 43378 deals the same problem.
*** Bug 43378 has been marked as a duplicate of this bug. ***
(In reply to comment #6) > I can confirm (Visual Basic 6 code) that with the quickstarter enabled > LibreOffice runs invisibly. Thanks for the hint. > > Bug 43378 deals the same problem. thanks for reminding me about that ( marked the other as duplicate ) and closing this as notabug
You are welcome. It would be possible to turn these reports into a feature request?
(In reply to comment #9) > You are welcome. > It would be possible to turn these reports into a feature request? It is possible always to submit a new bug to request any sort of change ( even to request a change to defaults ) but please don't reuse this bug, that imo would not be appropriate.
If it is not a bug, it is not a regression too, then regression keyword removed. Best regards. JBF