To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=25885
------- Additional comments from [EMAIL PROTECTED] Thu Aug 18 22:42:37 -0700 2005 ------- I want to give some background information why this is not so easy to realise. The main problem is that the information if a sub is private or not is only avai- lable inside the Basic core. But the Run/Assign Macro dialogs are based on the Scripting Framework API. So the information has to be provided somehow, probably by a new property the ScriptProvider for Basic has to support. And then the question occurs if it makes sense to provide a new property for this only reason or if it makes more sense to design a more general interface to provide information about subs/functions/methods (in the Scripting Framework context not only for Basic of course). I don't like a quick and dirty solution only to filter private Basic methods in UI. --------------------------------------------------------------------- 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]
