[sw-issues] [Issue 49110] Macro cannot be run if it is password protected.
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=49110 User tbe changed the following: What|Old value |New value Component|Word processor|framework QA contact|[EMAIL PROTECTED] |[EMAIL PROTECTED] Subcomponent|programming |code --- Additional comments from [EMAIL PROTECTED] Thu Jun 23 06:41:22 -0700 2005 --- set component framework - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 49110] Macro cannot be run if it is password protected.
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=49110 User tbe changed the following: What|Old value |New value Assigned to|tbe |ab --- Additional comments from [EMAIL PROTECTED] Thu Jun 23 06:28:21 -0700 2005 --- TBE->AB: Probably the target should be set to OOo 2.0 - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 49110] Macro cannot be run if it is password protected.
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=49110 User tbe changed the following: What|Old value |New value Attachment data| |Created an attachment | |(id=27446) | |myprotected1.odt (bug doc | |containing password | |protected library) --- Additional comments from [EMAIL PROTECTED] Thu Jun 23 06:26:50 -0700 2005 --- Created an attachment (id=27446) myprotected1.odt (bug doc containing password protected library) - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 49110] Macro cannot be run if it is password protected.
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=49110 --- Additional comments from [EMAIL PROTECTED] Thu Jun 23 06:24:52 -0700 2005 --- TBE->AB: The Run/OK button in the script selector is disabled, because the method browse node returns a script URL of lenght 0. In the BasicMethodNodeImpl CTOR (scripting/source/basprov/basmethnode.cxx) the call SbMethod::GetModule() returns NULL. A possible hack in the BasicMethodNodeImpl CTOR would be to use SbModule* pModule = static_cast< SbModule* >( m_pMethod->GetParent() ); instead of SbModule* pModule = m_pMethod->GetModule(); As this is only a hack, I propose to fix the bug in SbMethod::GetModule(). - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 49110] Macro cannot be run if it is password protected.
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=49110 --- Additional comments from [EMAIL PROTECTED] Thu Jun 23 04:44:39 -0700 2005 --- ab: I'm responsible for the Basic core in OOo / StarOffice and I just want to clarify some things. aijo, you're right: The password feature is only intended to protect the source code from beeing read and modified. Of course it must be possible to run the macros anyway. Everything else wouldn't make much sense, because why should anyone give away these macros at all then? It would be much easier to just keep them on the local disk to pro- tect them from anyone. So your scenario is exacly what this feature is ment for and it's a bug that the macros cannot be run. But probably it's only a problem of the user interface. The compiled code IS stored and it can be exe- cuted, if one manages to start it... ;-) Maybe it helps you to have some work arounds: You e.g. can integrate a small starter macro in the document's not protected Standard library. This macro can load the protected library by API and then can call any sub inside without knowing the password, e.g.: Sub NotProtectedStarterSub BasicLibraries.loadLibrary( "ProtectedLibrary" ) MySecretSub() ' Call into ProtectedLibrary End Sub You can also assign a sub inside the protected library to a control located in the document, e.g. to a button's "When initiating" event. When the user clicks on the button the protected library will be loaded automatically and the sub will be executed. tbe just made some tests and found that this can only be done before the library is protected. Afterwards - even if the correct password is entered - a macro inside the protected library cannot be assigned any more. We consider this to be part of this bug and it has to be fixed in any case. But anyway with knowing all this it should be possible for now to work around the problem. I hope this helps you. Andreas - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 49110] Macro cannot be run if it is password protected.
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=49110 User tbe changed the following: What|Old value |New value Ever confirmed| |1 Status|UNCONFIRMED |NEW Target milestone|--- |OOo 2.0.1 --- Additional comments from [EMAIL PROTECTED] Thu Jun 23 03:44:33 -0700 2005 --- set target to OOo 2.0.1 - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 49110] Macro cannot be run if it is password protected.
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=49110 --- Additional comments from [EMAIL PROTECTED] Thu Jun 23 02:39:59 -0700 2005 --- Hi all, My apology to everyone and Joerg especially, for commenting to him directly rather than here. The reason for the need of being able to run the macro while it is being password protected is to prevent the macro from being messed around. In a office environment we create macros to speed up work and most of the time make it easier to do things. But there are certain people who are too curious for their own good who open up the macro and start modifying the macro codes and ending up with a rather messed up program. At the end the objective to speed up work and make it easier gone to waste just to repair what they have done. I am not against anybody who is curious as I am a curious person too but I have seen too much of a problem in staff who, not happy with somebody, just messed up with somebody's work. I am also all for binary or object code compilation of the macro if it is in the planning. If it is not, I am proposing it :) Just like to mention again like I said to Mr Joerg himself that I really really appreciate what you guys are doing here. Thanks. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 49110] Macro cannot be run if it is password protected.
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=49110 User jsk changed the following: What|Old value |New value Assigned to|jsk |tbe --- Additional comments from [EMAIL PROTECTED] Thu Jun 23 02:13:56 -0700 2005 --- jsk->tbe: What do you think about this? - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 49110] Macro cannot be run if it is password protected.
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=49110 User jsk changed the following: What|Old value |New value Status|CLOSED|UNCONFIRMED Resolution|INVALID | --- Additional comments from [EMAIL PROTECTED] Thu Jun 23 02:12:34 -0700 2005 --- Hi Jo, Jo wrote: To me the reason the macro need to be password protected is to prevent it from being messed up by those just like to mess with it but certainly not to prevent it from being run. jsk: I think this is just not the way it works. I forward this issue to TBE to get a third opinion. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 49110] Macro cannot be run if it is password protected.
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=49110 User jsk changed the following: What|Old value |New value Status|RESOLVED |CLOSED --- Additional comments from [EMAIL PROTECTED] Thu Jun 23 00:05:14 -0700 2005 --- closing. aijo: If you do not agree, you can reopen the issue but there is little to no hope that we are going to change the behavior in the near future. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 49110] Macro cannot be run if it is password protected.
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=49110 User jsk changed the following: What|Old value |New value Status|UNCONFIRMED |RESOLVED Resolution| |INVALID --- Additional comments from [EMAIL PROTECTED] Thu Jun 23 00:02:48 -0700 2005 --- Hi aijo, i think you just found the reason for the password protection being there in the first place: Prevent people from using it if they do not have the password to unprotect it. ;) Joerg - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 49110] Macro cannot be run if it is password protected.
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=49110 User mru changed the following: What|Old value |New value Assigned to|mru |jsk --- Additional comments from [EMAIL PROTECTED] Wed May 11 09:21:30 -0700 2005 --- Reassigned to JSK. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]