To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=61194
                  Issue #:|61194
                  Summary:|[PATCH] allow user-defined channels for emitting
                          |diagnostic messages in non-product buids
                Component:|gsl
                  Version:|680m150
                 Platform:|All
                      URL:|
               OS/Version:|All
                   Status:|NEW
        Status whiteboard:|
                 Keywords:|
               Resolution:|
               Issue type:|PATCH
                 Priority:|P3
             Subcomponent:|code
              Assigned to:|pl
              Reported by:|fs





------- Additional comments from [EMAIL PROTECTED] Thu Jan 26 06:43:01 -0800 
2006 -------
There's a number of pre-defined channels to emit diagnostic error messages
(DBG_* from tools/debug.hxx) to: Window, Shell, MessageBox, TestTool, and so on.

It would be handy to allow user-defined channels, i.e. to register an arbitrary
channel with an arbitrary name, and an arbitrary DbgPrintLine.

The attached patch implements this.

The functionality does not have any use in itself, admittedly :)
However, doing complex test cases to test a number of UNO implementations, I
often stumbled over the problem that in non-product versions, the test seemingly
succeeded, but there were assertions during the test. Usual Java test cases
cannot capture those assertions, since they communicate with OOo via UNO only.
So my next step will be to write a UNO component (available in non-product
versions only) which re-routes the assertions to an own routine, and allows
other UNO clients to monitor those diagnostic messages :)

---------------------------------------------------------------------
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]

Reply via email to