To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=54416 Issue #:|54416 Summary:|pyuno logging Component:|udk Version:|OOO 2.0 Beta2 Platform:|All URL:| OS/Version:|All Status:|NEW Status whiteboard:| Keywords:| Resolution:| Issue type:|ENHANCEMENT Priority:|P3 Subcomponent:|code Assigned to:|jbu Reported by:|jbu
------- Additional comments from [EMAIL PROTECTED] Fri Sep 9 11:38:00 -0700 2005 ------- For analyzing various problems either within the pyuno bridge or with a concrete python script, a logging of all bridged pyuno calls is very helpful. This is currently implemented very rudimentary and could only be switched on by recompilation. Logging can now be switched on by bootstrap variables (e.g. using environment variables. There exist two variables: PYUNO_LOGLEVEL = [ NONE | CALL | ARGS ] (NONE is default) PYUNO_LOGTARGET = [ stdout | stderr | file-url-prefix(relative urls allowed) ] (stdout is default) (e.g. file://c:/temp/bla will write to c:\temp\bla.235 if 235 is the pid of the current process) Beside a timestamp, every bridged function call is logged (optionally with all in and out parameters). Logging is switched off by default. --------------------------------------------------------------------- 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]
