<html> <head> <title>Interface XDispatchRecorderSupplier</title> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <link rel="stylesheet" type="text/css" href="../../../../idl.css"> </head> <body> <div id="adc-idlref"> <a name="_top_"> </a><table class="navimain" border="0" cellpadding="3"> <tr> <td class="navimain"><a href="../module-ix.html" class="navimain">Overview</a></td> <td class="navimain"><a href="module-ix.html" class="navimain">Module</a></td> <td class="navimain"><a href="XDispatchRecorderSupplier-xref.html" class="navimain">Use</a></td> <td class="navimainnone">Devguide</td> <td class="navimain"><a href="../../../../index-files/index-1.html" class="navimain">Index</a></td> </tr> </table> <table class="navisub" border="0" cellpadding="0"> <tr> <td class="navisub"><a href="#MethodsSummary" class="navisub">Methods' Summary</a></td> <td class="navisub">Attributes' Summary</td> <td class="navisub"><a href="#MethodsDetails" class="navisub">Methods' Details</a></td> <td class="navisub">Attributes' Details</td> </tr> </table> <hr> <table border="0" width="100%" cellpadding="5" cellspacing="3" class="title-table" style="margin-bottom:6pt;"> <tr> <td><p class="namechain"><a href="../../../../module-ix.html" class="namechain">::</a> <a href="../../../module-ix.html" class="namechain">com</a> :: <a href="../../module-ix.html" class="namechain">sun</a> :: <a href="../module-ix.html" class="namechain">star</a> :: <a href="module-ix.html" class="namechain">frame</a> :: </p> </td> </tr> <tr> <td class="title">interface XDispatchRecorderSupplier</td> </tr> <tr> <td/></tr> <tr> <td><dl> <dt><b>Description</b></dt> <dd>provides access to the record mechanism of dispatches </dd> <dd><p> With a <a href="XDispatchRecorder.html">XDispatchRecorder</a> it's possible to record calls of <a href="XDispatch.html">XDispatch</a>::<a href="XDispatch.html#dispatch">dispatch()</a>. The recorded data (may a script) can be used to automate recorded dispatch and start it at later time again. This supplier provides access to the recorder and supports some functionality to work with the mcaro recording mechanism in an easy manner. </p> </dd> <dt><b>Since </b></dt> <dd>OpenOffice 1.1.2</dd> <dt><b>See also</b></dt> <dd><a href="XDispatchRecorder.html">XDispatchRecorder</a></dd> </dl> </td> </tr> </table> <hr> <a name="MethodsSummary"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle"> <tr> <td class="subtitle" colspan="2">Methods' Summary</td> </tr> <tr> <td class="imsum_left"><a href="#setDispatchRecorder">setDispatchRecorder</a></td> <td class="imsum_right">set a dispatch recorder on this supplier </td> </tr> <tr> <td class="imsum_left"><a href="#getDispatchRecorder">getDispatchRecorder</a></td> <td class="imsum_right">provides access on the recorder of this supplier </td> </tr> <tr> <td class="imsum_left"><a href="#dispatchAndRecord">dispatchAndRecord</a></td> <td class="imsum_right">dispatch given URL and record it if recording is enabled </td> </tr> </table> <a name="MethodsDetails"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle"> <tr> <td class="subtitle">Methods' Details</td> </tr> <tr> <td class="imdetail"><a name="setDispatchRecorder" class="membertitle">setDispatchRecorder</a><table border="0" width="96%" cellpadding="5" cellspacing="0" class="table-in-method" bgcolor="#ffffff" align="center"> <tr> <td><table class="table-in-method" border="0"> <tr> <td valign="top" colspan="3">void</td> </tr> <tr> <td valign="top"><b>setDispatchRecorder</b>(</td> <td valign="top">[in] <a href="XDispatchRecorder.html">XDispatchRecorder</a></td> <td valign="bottom"> Recorder );</td> </tr> </table> <hr> <dl> <dt><b>Description</b></dt> <dd>set a dispatch recorder on this supplier </dd> <dd><p> Setting of a new recorder make it possible to change recording mode. May there can exist different implementations of a recorder (e.g. to generate Java, Basic or other formats). Changing between local recording inside one <a href="Frame.html">Frame</a> or global one by using more then ones can be forced too. </p> </dd> <dt><b>Parameter Recorder</b></dt> <dd>the new recorder for this supplier </dd> </dl> </td> </tr> </table> </td> </tr> <tr> <td class="imdetail"><a name="getDispatchRecorder" class="membertitle">getDispatchRecorder</a><table border="0" width="96%" cellpadding="5" cellspacing="0" class="table-in-method" bgcolor="#ffffff" align="center"> <tr> <td><table class="table-in-method" border="0"> <tr> <td valign="top" colspan="3"><a href="XDispatchRecorder.html">XDispatchRecorder</a></td> </tr> <tr> <td valign="top"><b>getDispatchRecorder</b>();</td> </tr> </table> <hr> <dl> <dt><b>Description</b></dt> <dd>provides access on the recorder of this supplier </dd> <dd><p> Returned recorder can be used to record dispatches manualy or to get recorded data for further using e.g. saving. He is internaly used too due to the method <a href="XDispatchRecorderSupplier.html">XDispatchRecorderSupplier</a>::<a href="XDispatchRecorderSupplier.html#dispatchAndRecord">dispatchAndRecord()</a>. </p> </dd> <dt><b>Returns</b></dt> <dd>the dispatch recorder of this supplier </dd> <dt><b>See also</b></dt> <dd><a href="XDispatchRecorder.html">XDispatchRecorder</a></dd> </dl> </td> </tr> </table> </td> </tr> <tr> <td class="imdetail"><a name="dispatchAndRecord" class="membertitle">dispatchAndRecord</a><table border="0" width="96%" cellpadding="5" cellspacing="0" class="table-in-method" bgcolor="#ffffff" align="center"> <tr> <td><table class="table-in-method" border="0"> <tr> <td valign="top" colspan="3">void</td> </tr> <tr> <td valign="top"><b>dispatchAndRecord</b>(</td> <td valign="top">[in] ::com::sun::star::<a href="../util/module-ix.html">util</a>::<a href="../util/URL.html">URL</a></td> <td valign="bottom"> URL,</td> </tr> <tr> <td/><td valign="top">[in] sequence< ::com::sun::star::<a href="../beans/module-ix.html">beans</a>::<a href="../beans/PropertyValue.html">PropertyValue</a> ></td> <td valign="bottom"> Arguments,</td> </tr> <tr> <td/><td valign="top">[in] <a href="XDispatch.html">XDispatch</a></td> <td valign="bottom"> Dispatcher );</td> </tr> </table> <hr> <dl> <dt><b>Description</b></dt> <dd>dispatch given URL and record it if recording is enabled </dd> <dd><p> Parameter <var>Dispatcher</var> is used internaly to make the dispatch. If recording isn't enabled it will be a normal <a href="XDispatch.html">XDispatch</a>::<a href="XDispatch.html#dispatch">dispatch()</a> call. Otherwise follow algorithm is used: <ul> <li>If <var>Dispatcher</var> doesn't support the interface <a href="XRecordableDispatch.html">XRecordableDispatch</a> a normal dispatch() call will be made and depend from the result state of that the request will be recorded. In this case it's possible to record the incoming parameter (<var>URL</var> and <var>Arguments</var>) only. Parameters of internal processes can't be recorded then and will be lost. </li> <li>If <var>Dispatcher</var> support the interface <a href="XRecordableDispatch.html">XRecordableDispatch</a> it will be used to dispatch and record all neccessary parameters of the whole process. </li> </ul> </p> </dd> <dt><b>See also</b></dt> <dd><a href="XRecordableDispatch.html">XRecordableDispatch</a></dd> </dl> </td> </tr> </table> </td> </tr> </table> <a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.</p> </div> <!-- id="adc-idlref" --> </body> </html>
distrib
>
Mandriva
>
current
>
i586
>
media
>
main-updates
>
by-pkgid
>
fc480f9d5aabed8eeaffe8ad3401a94c
>
files
>
3535
