<html> <head> <title>Interface XPlotter</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="XPlotter-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"><a href="#MethodsDetails" class="navisub">Methods' Details</a></td> <td class="navisub">Attributes' Summary</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">chart2</a> :: </p> </td> </tr> <tr> <td class="title">interface XPlotter</td> </tr> <tr> <td/></tr> <tr> <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="#getCoordinateSystemTypeID">getCoordinateSystemTypeID</a></td> <td class="imsum_right">Each Plotter implicit uses a certain type of logic coordinate system for interpreting data as coordinates. For example a bar-chart uses a cartesian coordinate system for interpreting x- and y-values from a spreadsheet as cartesian coordinates. In contrast the pie chart assumes a polar coordinate system. The type of this implicit used source coordinate system has to be returned here. The returned type of an implementation never changes. </td> </tr> <tr> <td class="imsum_left"><a href="#init">init</a></td> <td class="imsum_right">For each type of shapes ('logic' or 'illogic') there exists one container. The Plotter will create shapes and then add (or remove) them from these containers. </td> </tr> <tr> <td class="imsum_left"><a href="#setScales">setScales</a></td> <td class="imsum_right">For each dimension of the 'logic source coordinate system' the XPlotter object needs a Scale to decide which shapes need to be created and maybe logically clipped. The XPlotter object becomes the new owner of the given scales and directions and needs to keep them alive. Nobody else will change them. Pay attention that a 'Scale' can have several breaks. </td> </tr> <tr> <td class="imsum_left"><a href="#setTransformation">setTransformation</a></td> <td class="imsum_right"> </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="getCoordinateSystemTypeID" class="membertitle">getCoordinateSystemTypeID</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="CoordinateSystemTypeID.html">CoordinateSystemTypeID</a></td> </tr> <tr> <td valign="top"><b>getCoordinateSystemTypeID</b>();</td> </tr> </table> <hr> <dl> <dt><b>Description</b></dt> <dd>Each Plotter implicit uses a certain type of logic coordinate system for interpreting data as coordinates. For example a bar-chart uses a cartesian coordinate system for interpreting x- and y-values from a spreadsheet as cartesian coordinates. In contrast the pie chart assumes a polar coordinate system. The type of this implicit used source coordinate system has to be returned here. The returned type of an implementation never changes. </dd> </dl> </td> </tr> </table> </td> </tr> <tr> <td class="imdetail"><a name="init" class="membertitle">init</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>init</b>(</td> <td valign="top">[in] ::com::sun::star::<a href="../drawing/module-ix.html">drawing</a>::<a href="../drawing/XShapes.html">XShapes</a></td> <td valign="bottom"> xLogicTarget,</td> </tr> <tr> <td/><td valign="top">[in] ::com::sun::star::<a href="../drawing/module-ix.html">drawing</a>::<a href="../drawing/XShapes.html">XShapes</a></td> <td valign="bottom"> xFinalTarget,</td> </tr> <tr> <td/><td valign="top">[in] ::com::sun::star::<a href="../lang/module-ix.html">lang</a>::<a href="../lang/XMultiServiceFactory.html">XMultiServiceFactory</a></td> <td valign="bottom"> xFactory );</td> </tr> </table> <hr> <dl> <dt><b>Description</b></dt> <dd>For each type of shapes ('logic' or 'illogic') there exists one container. The Plotter will create shapes and then add (or remove) them from these containers. </dd> <dd><p> The lifetime of the container has to be handled by the calling object. The calling object must assure that the container will exist longer than the XPlotter Object. </p> ... </dd> </dl> </td> </tr> </table> </td> </tr> <tr> <td class="imdetail"><a name="setScales" class="membertitle">setScales</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>setScales</b>(</td> <td valign="top">[in] sequence< <a href="ScaleData.html">ScaleData</a> ></td> <td valign="bottom"> rScales );</td> </tr> </table> <hr> <dl> <dt><b>Description</b></dt> <dd>For each dimension of the 'logic source coordinate system' the XPlotter object needs a Scale to decide which shapes need to be created and maybe logically clipped. The XPlotter object becomes the new owner of the given scales and directions and needs to keep them alive. Nobody else will change them. Pay attention that a 'Scale' can have several breaks. </dd> </dl> </td> </tr> </table> </td> </tr> <tr> <td class="imdetail"><a name="setTransformation" class="membertitle">setTransformation</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>setTransformation</b>(</td> <td valign="top">[in] <a href="XTransformation.html">XTransformation</a></td> <td valign="bottom"> xTransformationToLogicTarget,</td> </tr> <tr> <td/><td valign="top">[in] <a href="XTransformation.html">XTransformation</a></td> <td valign="bottom"> xTransformationToFinalPage );</td> </tr> </table> <hr> <dl></dl> </td> </tr> </table> </td> </tr> </table> <a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright © 2008 Sun Microsystems, Inc.</p> </div> <!-- id="adc-idlref" --> </body> </html>