Apache OpenOffice (AOO) Bugzilla – Issue 25222
api call & macro regression
Last modified: 2013-02-24 21:08:52 UTC
Hi, these macro works on OOo1.1.0 Sub go launcher = CreateUnoService("com.sun.star.system.SystemShellExecute") Adresse="http://www.google.com" launcher.execute(Adresse, "", 0) End Sub using it under OOo1.1.1b gives an error Basic Runtime error property or method not found using isNull and IsEmpty gives False --> execute method seems to be broken Laurent
@Tino: I guess, it's your area?
forwarding
Hi! Please verify that there is a library syssh.dll in you OOo\program directory and this library was registered successfully during installation (no installation errors, have a look at the setup log file). Furthermore you may try if a browser with your requested address pops up if you enter the address into the address panel in the Windows XP task bar. In order to display the address panel right click the Windows XP task bar and select "Toolbars->Address" from the appearing context menu. If all this works there may be indeed a problem with the service althought there were no changes in this area for a long period. BTW: I couldn't reproduce the problem with a current version of StarOffice. Kind Regards, Tino
Hi here are the results of the tests you required program/syssh.dll: version : 7.0.0.8739 size : 17 408 date: 31/01/2004 01:10 setup.log: OK register component: syssh.dll : services.rdb WinXP address toolbar Works Thanks Laurent
Hi Laurent, thanks for your quick response. Seems that we have a weird problem here. I will investigate whats going on. Kind Regards, Tino
Hi Laurent, I can confirm the problem. Even copying the sysshl.dll from my working StarOffice installation to the OOo\progrm folder doesn't help. Seems that there is a Basic problem. I will talk to the Basic guys tomorrow before I start debugging myself. Kind Regards, Tino
Hi Laurent, the cause of the problem is now known. In the OOo1.1.1b installation you find a macro module named "Launcher" (have a look at the macro list). There is a name clash between this name and the name of the variable 'launcher' in your macro. If you rename this variable everything works fine. I know that this is no real solution as it's should not happen that the addition of a macro module influences the function of an arbitrary macro but it's not a problem of the shell executer service. Maybe the basic guys could help. Kind Regards, Tino
Hi Tino, Thanks a lot for your clear response ! I confirm as i reproduced the problem with an other library name used as a variable I redirect this Issue to Andreas Bregas (aka ab ?) (which seems to me a Basic Guru :) ) Thanks again Laurent
Hi Laurent, from my point of view this cannot be fixed. Library names are mapped into the global scope to allow explicit adressing like MyLib.MyModule.doit(42). So if a new library is included all equally named identfiers conflict with it. But it's neither possible to remove the library name mapping (then no program using this feature would run any more) nor to prevent new libraries from beeing added to share/basic. The only way to avoid this is to use less generic indentifiers in programs. Andreas
Hi Andreas, Ok ! But what about a more explicit message "Redundant varaible name" or "variable already defined" or something else Laurent
It's very difficult to detect if a user wants to access an already existing object or if there's a name conflict. I see no chance for now -> closed