incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ksch...@apache.org
Subject svn commit: r1206299 [16/19] - in /incubator/ooo/ooo-site/trunk/content/gsl: canvas/ canvas/api/ canvas/api/geometry/ canvas/api/index-files/ canvas/api/rendering/ psprint/ vcl/ vcl/plugins/
Date Fri, 25 Nov 2011 20:07:51 GMT
Added: incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XGraphicDevice.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XGraphicDevice.html?rev=1206299&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XGraphicDevice.html (added)
+++ incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XGraphicDevice.html Fri Nov 25 20:06:37 2011
@@ -0,0 +1,638 @@
+<html>
+<head>
+<title>Interface XGraphicDevice</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="XGraphicDevice-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">rendering</a> :: </p>
+</td>
+</tr>
+<tr>
+<td class="title"><table class="title-table" width="99%">
+<tr>
+<td width="25%" class="title2">unpublished </td>
+<td width="50%" class="title">interface XGraphicDevice</td>
+<td width="*"/></tr>
+</table>
+</td>
+</tr>
+<tr>
+<td><dl>
+<dt><b>Base Interfaces</b></dt>
+<dd><pre style="font-family:monospace;"><strong>XGraphicDevice</strong>
+&#x2517 ::com::sun::star::uno::XInterface
+
+</pre></dd>
+<dd><a name/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="crosstitle">
+<tr>
+<td class="imsum_left">::com::sun::star::uno::XInterface</td>
+<td class="imsum_right"><dl></dl>
+</td>
+</tr>
+</table>
+</dd>
+</dl>
+</td>
+</tr>
+<tr>
+<td><dl>
+<dt><b>Description</b></dt>
+<dd>This interface provides access to a graphic device, such as a 
+printer, or a screen device. Every canvas ( </dd>
+<dt><b>See also</b></dt>
+<dd>XCanvas)<br>
+has 
+exactly one associated graphic device, into which its output is 
+rendered. 
+
+For a typical windowing system, the graphic device is equivalent 
+to a distinct OS window, with it's own clipped output area, 
+fullscreen and double-buffering attributes. That is, even if one 
+can have multiple canvases per system window, they all share the 
+same graphic device and thus e.g. fullscreen state. If the OS 
+restrictions are in such a way that fullscreen or double-buffering 
+is screen-exclusive, i.e. that per screen, only one object can 
+have this state, it might even be that all windows on the screen 
+share a common graphic device. 
+</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="#getBufferController">getBufferController</a></td>
+<td class="imsum_right">Query the controller for multi buffering functionality on this 
+graphic device. 
+
+If there is no such functionality available, the NULL 
+reference is returned. 
+&nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#getDeviceColorSpace">getDeviceColorSpace</a></td>
+<td class="imsum_right">Query the color space interface for this graphic device. 
+
+This is to be used when interpreting or setting device color 
+values. 
+&nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#getPhysicalResolution">getPhysicalResolution</a></td>
+<td class="imsum_right">Query the physical resolution of the device in pixel per 
+millimeter. 
+
+A special floating point value of +infinity here indicates 
+'unknown', i.e. at the time of rendering undetermined or 
+possibly infinite resolution along the corresponding 
+direction. 
+&nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#getPhysicalSize">getPhysicalSize</a></td>
+<td class="imsum_right">Query the physical dimensions of the device in millimeter. 
+
+A special floating point value of +infinity here indicates 
+'unknown', i.e. at the time of rendering undetermined or 
+possibly infinite resolution along the corresponding 
+direction. 
+
+&nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#createCompatibleLinePolyPolygon">createCompatibleLinePolyPolygon</a></td>
+<td class="imsum_right">Create a line poly-polygon which can internally use 
+device-optimized representations already. 
+
+&nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#createCompatibleBezierPolyPolygon">createCompatibleBezierPolyPolygon</a></td>
+<td class="imsum_right">Create a bezier poly-polygon which can internally use 
+device-optimized representations already. 
+
+&nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#createCompatibleBitmap">createCompatibleBitmap</a></td>
+<td class="imsum_right">Create a bitmap whose memory layout and sample model is 
+compatible to the graphic device. 
+
+&nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#createVolatileBitmap">createVolatileBitmap</a></td>
+<td class="imsum_right">Create a volatile bitmap that is usable with this graphic device. 
+
+A volatile bitmap's difference in comparison to a plain bitmap 
+(e.g. generated via createCompatibleBitmap()) is the fact that 
+its content might vanish at any point in time (making any 
+operation with them produce a 
+<a href="VolatileContentDestroyedException.html">VolatileContentDestroyedException</a> ). The benefit, 
+on the other hand, is that they might be easy to 
+hardware-accelerate on certain platforms, without the need to 
+keep a safety copy of the content internally. 
+
+&nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#createCompatibleAlphaBitmap">createCompatibleAlphaBitmap</a></td>
+<td class="imsum_right">Create a bitmap with alpha channel whose memory layout and 
+sample model is compatible to the graphic device. 
+
+&nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#createVolatileAlphaBitmap">createVolatileAlphaBitmap</a></td>
+<td class="imsum_right">Create a volatile bitmap with alpha channel that is usable 
+with this graphic device. 
+
+A volatile bitmap's difference in comparison to a plain bitmap 
+(e.g. generated via createCompatibleBitmap()) is the fact that 
+its content might vanish at any point in time (making any 
+operation with them produce a 
+<a href="VolatileContentDestroyedException.html">VolatileContentDestroyedException</a> ). The benefit, 
+on the other hand, is that they might be easy to 
+hardware-accelerate on certain platforms, without the need to 
+keep a safety copy of the content internally. 
+
+&nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#getParametricPolyPolygonFactory">getParametricPolyPolygonFactory</a></td>
+<td class="imsum_right">Get a reference to this device's parametric polygon factory. 
+
+&nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#hasFullScreenMode">hasFullScreenMode</a></td>
+<td class="imsum_right">Tells whether this graphic device has a full screen mode, 
+i.e. whether a window can cover the whole screen exclusively. 
+&nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#enterFullScreenMode">enterFullScreenMode</a></td>
+<td class="imsum_right">Enter or leave the fullscreen mode, if possible. The return 
+value denotes the success of the operation. 
+
+@attention depending on the underlying operating system, 
+fullscreen mode can be left without a enterFullScreenMode( 
+false ) call. 
+&nbsp;</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="getBufferController" class="membertitle">getBufferController</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="XBufferController.html">XBufferController</a></td>
+</tr>
+<tr>
+<td valign="top"><b>getBufferController</b>();</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Query the controller for multi buffering functionality on this 
+graphic device. 
+
+If there is no such functionality available, the NULL 
+reference is returned. 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="getDeviceColorSpace" class="membertitle">getDeviceColorSpace</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="XColorSpace.html">XColorSpace</a></td>
+</tr>
+<tr>
+<td valign="top"><b>getDeviceColorSpace</b>();</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Query the color space interface for this graphic device. 
+
+This is to be used when interpreting or setting device color 
+values. 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="getPhysicalResolution" class="membertitle">getPhysicalResolution</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">::com::sun::star::geometry::RealSize2D</td>
+</tr>
+<tr>
+<td valign="top"><b>getPhysicalResolution</b>();</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Query the physical resolution of the device in pixel per 
+millimeter. 
+
+A special floating point value of +infinity here indicates 
+'unknown', i.e. at the time of rendering undetermined or 
+possibly infinite resolution along the corresponding 
+direction. 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="getPhysicalSize" class="membertitle">getPhysicalSize</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">::com::sun::star::geometry::RealSize2D</td>
+</tr>
+<tr>
+<td valign="top"><b>getPhysicalSize</b>();</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Query the physical dimensions of the device in millimeter. 
+
+A special floating point value of +infinity here indicates 
+'unknown', i.e. at the time of rendering undetermined or 
+possibly infinite resolution along the corresponding 
+direction. 
+
+</dd>
+<dt><b>See also</b></dt>
+<dd><a href="XBitmap.html">XBitmap</a>::<a href="XBitmap.html#getSize">getSize()</a></dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="createCompatibleLinePolyPolygon" class="membertitle">createCompatibleLinePolyPolygon</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="XLinePolyPolygon2D.html">XLinePolyPolygon2D</a></td>
+</tr>
+<tr>
+<td valign="top"><b>createCompatibleLinePolyPolygon</b>(</td>
+<td valign="top">[in] sequence&lt; sequence&lt; ::com::sun::star::geometry::RealPoint2D &gt; &gt;</td>
+<td valign="bottom">&nbsp;points );</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Create a line poly-polygon which can internally use 
+device-optimized representations already. 
+
+</dd>
+<dt><b>Parameter points</b></dt>
+<dd>The points of the poly-polygon, in a separate array for every polygon. 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="createCompatibleBezierPolyPolygon" class="membertitle">createCompatibleBezierPolyPolygon</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="XBezierPolyPolygon2D.html">XBezierPolyPolygon2D</a></td>
+</tr>
+<tr>
+<td valign="top"><b>createCompatibleBezierPolyPolygon</b>(</td>
+<td valign="top">[in] sequence&lt; sequence&lt; ::com::sun::star::geometry::RealBezierSegment2D &gt; &gt;</td>
+<td valign="bottom">&nbsp;points );</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Create a bezier poly-polygon which can internally use 
+device-optimized representations already. 
+
+</dd>
+<dt><b>Parameter points</b></dt>
+<dd>The points of the poly-polygon, in a separate array for every polygon. 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="createCompatibleBitmap" class="membertitle">createCompatibleBitmap</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="XBitmap.html">XBitmap</a></td>
+</tr>
+<tr>
+<td valign="top"><b>createCompatibleBitmap</b>(</td>
+<td valign="top">[in] ::com::sun::star::geometry::IntegerSize2D</td>
+<td valign="bottom">&nbsp;size )</td>
+</tr>
+<tr>
+<td valign="top" align="right">raises( </td>
+<td valign="top" colspan="2">::com::sun::star::lang::IllegalArgumentException );</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Create a bitmap whose memory layout and sample model is 
+compatible to the graphic device. 
+
+</dd>
+<dt><b>Parameter size</b></dt>
+<dd>Size of the requested bitmap in pixel. Both components of the 
+size must be greater than 0 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="createVolatileBitmap" class="membertitle">createVolatileBitmap</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="XVolatileBitmap.html">XVolatileBitmap</a></td>
+</tr>
+<tr>
+<td valign="top"><b>createVolatileBitmap</b>(</td>
+<td valign="top">[in] ::com::sun::star::geometry::IntegerSize2D</td>
+<td valign="bottom">&nbsp;size )</td>
+</tr>
+<tr>
+<td valign="top" align="right">raises( </td>
+<td valign="top" colspan="2">::com::sun::star::lang::IllegalArgumentException );</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Create a volatile bitmap that is usable with this graphic device. 
+
+A volatile bitmap's difference in comparison to a plain bitmap 
+(e.g. generated via createCompatibleBitmap()) is the fact that 
+its content might vanish at any point in time (making any 
+operation with them produce a 
+<a href="VolatileContentDestroyedException.html">VolatileContentDestroyedException</a> ). The benefit, 
+on the other hand, is that they might be easy to 
+hardware-accelerate on certain platforms, without the need to 
+keep a safety copy of the content internally. 
+
+</dd>
+<dt><b>Parameter size</b></dt>
+<dd>Size of the requested bitmap in pixel. Both components of the 
+size must be greater than 0 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="createCompatibleAlphaBitmap" class="membertitle">createCompatibleAlphaBitmap</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="XBitmap.html">XBitmap</a></td>
+</tr>
+<tr>
+<td valign="top"><b>createCompatibleAlphaBitmap</b>(</td>
+<td valign="top">[in] ::com::sun::star::geometry::IntegerSize2D</td>
+<td valign="bottom">&nbsp;size )</td>
+</tr>
+<tr>
+<td valign="top" align="right">raises( </td>
+<td valign="top" colspan="2">::com::sun::star::lang::IllegalArgumentException );</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Create a bitmap with alpha channel whose memory layout and 
+sample model is compatible to the graphic device. 
+
+</dd>
+<dt><b>Parameter size</b></dt>
+<dd>Size of the requested bitmap in pixel. Both components of the 
+size must be greater than 0 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="createVolatileAlphaBitmap" class="membertitle">createVolatileAlphaBitmap</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="XVolatileBitmap.html">XVolatileBitmap</a></td>
+</tr>
+<tr>
+<td valign="top"><b>createVolatileAlphaBitmap</b>(</td>
+<td valign="top">[in] ::com::sun::star::geometry::IntegerSize2D</td>
+<td valign="bottom">&nbsp;size )</td>
+</tr>
+<tr>
+<td valign="top" align="right">raises( </td>
+<td valign="top" colspan="2">::com::sun::star::lang::IllegalArgumentException );</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Create a volatile bitmap with alpha channel that is usable 
+with this graphic device. 
+
+A volatile bitmap's difference in comparison to a plain bitmap 
+(e.g. generated via createCompatibleBitmap()) is the fact that 
+its content might vanish at any point in time (making any 
+operation with them produce a 
+<a href="VolatileContentDestroyedException.html">VolatileContentDestroyedException</a> ). The benefit, 
+on the other hand, is that they might be easy to 
+hardware-accelerate on certain platforms, without the need to 
+keep a safety copy of the content internally. 
+
+</dd>
+<dt><b>Parameter size</b></dt>
+<dd>Size of the requested bitmap in pixel. Both components of the 
+size must be greater than 0 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="getParametricPolyPolygonFactory" class="membertitle">getParametricPolyPolygonFactory</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="XParametricPolyPolygon2DFactory.html">XParametricPolyPolygon2DFactory</a></td>
+</tr>
+<tr>
+<td valign="top"><b>getParametricPolyPolygonFactory</b>();</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Get a reference to this device's parametric polygon factory. 
+
+</dd>
+<dt><b>Returns</b></dt>
+<dd>a reference to this device's parametric polygon 
+factory. Although it is possible to use parametric polygons on 
+all canvases, regardless of the associated graphic device, 
+this is not advisable: each canvas implementation is free to 
+internally generate optimized parametric polygons, which can 
+be used more directly for e.g. texturing operations. 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="hasFullScreenMode" class="membertitle">hasFullScreenMode</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">boolean</td>
+</tr>
+<tr>
+<td valign="top"><b>hasFullScreenMode</b>();</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Tells whether this graphic device has a full screen mode, 
+i.e. whether a window can cover the whole screen exclusively. 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="enterFullScreenMode" class="membertitle">enterFullScreenMode</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">boolean</td>
+</tr>
+<tr>
+<td valign="top"><b>enterFullScreenMode</b>(</td>
+<td valign="top">[in] boolean</td>
+<td valign="bottom">&nbsp;bEnter );</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Enter or leave the fullscreen mode, if possible. The return 
+value denotes the success of the operation. 
+
+@attention depending on the underlying operating system, 
+fullscreen mode can be left without a enterFullScreenMode( 
+false ) call. 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright &copy; 2003 Sun Microsystems, Inc.</p>
+
+</div> <!-- id="adc-idlref" -->
+</body>
+
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XGraphicDevice.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XHalfFloatBitmap-xref.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XHalfFloatBitmap-xref.html?rev=1206299&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XHalfFloatBitmap-xref.html (added)
+++ incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XHalfFloatBitmap-xref.html Fri Nov 25 20:06:37 2011
@@ -0,0 +1,55 @@
+<html>
+<head>
+<title>Uses of Interface XHalfFloatBitmap-xref</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="navimainself">Use</td>
+<td class="navimainnone">Devguide</td>
+<td class="navimain"><a href="../../../../index-files/index-1.html" class="navimain">Index</a></td>
+</tr>
+</table>
+<hr>
+<table border="0" width="100%" cellpadding="5" cellspacing="3" class="title-table" style="margin-bottom:6pt;">
+<tr>
+<td class="title">uses of interface XHalfFloatBitmap</td>
+</tr>
+<tr>
+<td><p><a href="XHalfFloatBitmap.html"><b>back to interface XHalfFloatBitmap</b></a><br>
+<br>
+
+Derived Interfaces<br>
+
+Synonym Typedefs<br>
+
+Services which Support this Interface<br>
+
+Singletons which Support this Interface<br>
+
+Uses as Return Type<br>
+
+Uses as Parameter<br>
+
+Uses as Data Type<br>
+
+References in Developers Guide<br>
+
+</p>
+</td>
+</tr>
+</table>
+<hr>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright &copy; 2003 Sun Microsystems, Inc.</p>
+
+</div> <!-- id="adc-idlref" -->
+</body>
+
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XHalfFloatBitmap-xref.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XHalfFloatBitmap.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XHalfFloatBitmap.html?rev=1206299&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XHalfFloatBitmap.html (added)
+++ incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XHalfFloatBitmap.html Fri Nov 25 20:06:37 2011
@@ -0,0 +1,339 @@
+<html>
+<head>
+<title>Interface XHalfFloatBitmap</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="XHalfFloatBitmap-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">rendering</a> :: </p>
+</td>
+</tr>
+<tr>
+<td class="title"><table class="title-table" width="99%">
+<tr>
+<td width="25%" class="title2">unpublished </td>
+<td width="50%" class="title">interface XHalfFloatBitmap</td>
+<td width="*"/></tr>
+</table>
+</td>
+</tr>
+<tr>
+<td><dl>
+<dt><b>Base Interfaces</b></dt>
+<dd><pre style="font-family:monospace;"><strong>XHalfFloatBitmap</strong>
+&#x2517 <a href="XBitmap.html">XBitmap</a>
+   &#x2517 ::com::sun::star::uno::XInterface
+
+</pre></dd>
+<dd><a name/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="crosstitle">
+<tr>
+<td class="imsum_left"><a href="XBitmap.html">XBitmap</a></td>
+<td class="imsum_right"><dl>
+<dt>(referenced interface's summary:)</dt>
+<dd>This is a generic interface to a bitmap. </dd>
+</dl>
+</td>
+</tr>
+</table>
+</dd>
+</dl>
+</td>
+</tr>
+<tr>
+<td><dl>
+<dt><b>Description</b></dt>
+<dd>Specialized interface for bitmaps containing half floats as their 
+color components. Half floats are 16 bit wide, and some high-end 
+GPUs already have them as supported frame buffer format. 
+</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="#getData">getData</a></td>
+<td class="imsum_right">Query the raw data of this bitmap. 
+
+Query the raw data of this bitmap, in the format as defined by 
+getMemoryLayout(). With the given rectangle, a subset of the 
+whole bitmap can be queried. When querying subsets of the 
+bitmap, the same scanline padding takes place as when the 
+whole bitmap is requested. Note: as we currently have no 16 
+bit float UNO data type, the values are transported as 16 bit 
+integers across the API (which requires casting on both 
+sides). 
+
+&nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#setData">setData</a></td>
+<td class="imsum_right">Set raw data of a bitmap. 
+
+Set raw data of a bitmap, in the format as defined by 
+getMemoryLayout(). With the given rectangle, a subset of the 
+bitmap can be changed. When setting subsets of the bitmap, the 
+same scanline padding takes place as when the whole bitmap is 
+changed. &nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#setPixel">setPixel</a></td>
+<td class="imsum_right">Set a single pixel of the bitmap with the given color 
+value. 
+
+When setting data on volatile bitmaps, always call isValid() 
+before, and retrieve a new memory layout via 
+getMemoryLayout(). At least under Windows, the memory layout 
+can change for the same bitmap, if the user e.g. switches the 
+screen resolution. Thus, this method will throw an 
+IllegalArgumentException, if the memory layout changed between 
+a call to getMemoryLayout() and setData(). 
+&nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#getPixel">getPixel</a></td>
+<td class="imsum_right">Get a single pixel of the bitmap, returning its color 
+value. 
+
+&nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#getMemoryLayout">getMemoryLayout</a></td>
+<td class="imsum_right">Query the memory layout for this bitmap 
+&nbsp;</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="getData" class="membertitle">getData</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">sequence&lt; short &gt;</td>
+</tr>
+<tr>
+<td valign="top"><b>getData</b>(</td>
+<td valign="top">[in] ::com::sun::star::geometry::IntegerRectangle2D</td>
+<td valign="bottom">&nbsp;rect )</td>
+</tr>
+<tr>
+<td valign="top" align="right">raises( </td>
+<td valign="top" colspan="2">::com::sun::star::lang::IndexOutOfBoundsException,<br>
+<a href="VolatileContentDestroyedException.html">VolatileContentDestroyedException</a> );</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Query the raw data of this bitmap. 
+
+Query the raw data of this bitmap, in the format as defined by 
+getMemoryLayout(). With the given rectangle, a subset of the 
+whole bitmap can be queried. When querying subsets of the 
+bitmap, the same scanline padding takes place as when the 
+whole bitmap is requested. Note: as we currently have no 16 
+bit float UNO data type, the values are transported as 16 bit 
+integers across the API (which requires casting on both 
+sides). 
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd>VolatileContentDestroyedException 
+if the bitmap is volatile, and the content has been destroyed by the system. 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="setData" class="membertitle">setData</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>setData</b>(</td>
+<td valign="top">[in] sequence&lt; short &gt;</td>
+<td valign="bottom">&nbsp;data,</td>
+</tr>
+<tr>
+<td/><td valign="top">[in] <a href="FloatingPointBitmapLayout.html">FloatingPointBitmapLayout</a></td>
+<td valign="bottom">&nbsp;bitmapLayout,</td>
+</tr>
+<tr>
+<td/><td valign="top">[in] ::com::sun::star::geometry::IntegerRectangle2D</td>
+<td valign="bottom">&nbsp;rect )</td>
+</tr>
+<tr>
+<td valign="top" align="right">raises( </td>
+<td valign="top" colspan="2">::com::sun::star::lang::IllegalArgumentException,<br>
+::com::sun::star::lang::IndexOutOfBoundsException );</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Set raw data of a bitmap. 
+
+Set raw data of a bitmap, in the format as defined by 
+getMemoryLayout(). With the given rectangle, a subset of the 
+bitmap can be changed. When setting subsets of the bitmap, the 
+same scanline padding takes place as when the whole bitmap is 
+changed. </dd>
+<dd><p>
+
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="setPixel" class="membertitle">setPixel</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>setPixel</b>(</td>
+<td valign="top">[in] sequence&lt; short &gt;</td>
+<td valign="bottom">&nbsp;color,</td>
+</tr>
+<tr>
+<td/><td valign="top">[in] <a href="FloatingPointBitmapLayout.html">FloatingPointBitmapLayout</a></td>
+<td valign="bottom">&nbsp;bitmapLayout,</td>
+</tr>
+<tr>
+<td/><td valign="top">[in] ::com::sun::star::geometry::IntegerPoint2D</td>
+<td valign="bottom">&nbsp;pos )</td>
+</tr>
+<tr>
+<td valign="top" align="right">raises( </td>
+<td valign="top" colspan="2">::com::sun::star::lang::IllegalArgumentException,<br>
+::com::sun::star::lang::IndexOutOfBoundsException );</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Set a single pixel of the bitmap with the given color 
+value. 
+
+When setting data on volatile bitmaps, always call isValid() 
+before, and retrieve a new memory layout via 
+getMemoryLayout(). At least under Windows, the memory layout 
+can change for the same bitmap, if the user e.g. switches the 
+screen resolution. Thus, this method will throw an 
+IllegalArgumentException, if the memory layout changed between 
+a call to getMemoryLayout() and setData(). 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="getPixel" class="membertitle">getPixel</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">sequence&lt; short &gt;</td>
+</tr>
+<tr>
+<td valign="top"><b>getPixel</b>(</td>
+<td valign="top">[in] ::com::sun::star::geometry::IntegerPoint2D</td>
+<td valign="bottom">&nbsp;pos )</td>
+</tr>
+<tr>
+<td valign="top" align="right">raises( </td>
+<td valign="top" colspan="2">::com::sun::star::lang::IndexOutOfBoundsException,<br>
+<a href="VolatileContentDestroyedException.html">VolatileContentDestroyedException</a> );</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Get a single pixel of the bitmap, returning its color 
+value. 
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd>VolatileContentDestroyedException 
+if the bitmap is volatile, and the content has been destroyed by the system. 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="getMemoryLayout" class="membertitle">getMemoryLayout</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="FloatingPointBitmapLayout.html">FloatingPointBitmapLayout</a></td>
+</tr>
+<tr>
+<td valign="top"><b>getMemoryLayout</b>();</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Query the memory layout for this bitmap 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright &copy; 2003 Sun Microsystems, Inc.</p>
+
+</div> <!-- id="adc-idlref" -->
+</body>
+
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XHalfFloatBitmap.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIeeeDoubleBitmap-xref.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIeeeDoubleBitmap-xref.html?rev=1206299&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIeeeDoubleBitmap-xref.html (added)
+++ incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIeeeDoubleBitmap-xref.html Fri Nov 25 20:06:37 2011
@@ -0,0 +1,55 @@
+<html>
+<head>
+<title>Uses of Interface XIeeeDoubleBitmap-xref</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="navimainself">Use</td>
+<td class="navimainnone">Devguide</td>
+<td class="navimain"><a href="../../../../index-files/index-1.html" class="navimain">Index</a></td>
+</tr>
+</table>
+<hr>
+<table border="0" width="100%" cellpadding="5" cellspacing="3" class="title-table" style="margin-bottom:6pt;">
+<tr>
+<td class="title">uses of interface XIeeeDoubleBitmap</td>
+</tr>
+<tr>
+<td><p><a href="XIeeeDoubleBitmap.html"><b>back to interface XIeeeDoubleBitmap</b></a><br>
+<br>
+
+Derived Interfaces<br>
+
+Synonym Typedefs<br>
+
+Services which Support this Interface<br>
+
+Singletons which Support this Interface<br>
+
+Uses as Return Type<br>
+
+Uses as Parameter<br>
+
+Uses as Data Type<br>
+
+References in Developers Guide<br>
+
+</p>
+</td>
+</tr>
+</table>
+<hr>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright &copy; 2003 Sun Microsystems, Inc.</p>
+
+</div> <!-- id="adc-idlref" -->
+</body>
+
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIeeeDoubleBitmap-xref.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIeeeDoubleBitmap.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIeeeDoubleBitmap.html?rev=1206299&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIeeeDoubleBitmap.html (added)
+++ incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIeeeDoubleBitmap.html Fri Nov 25 20:06:37 2011
@@ -0,0 +1,445 @@
+<html>
+<head>
+<title>Interface XIeeeDoubleBitmap</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="XIeeeDoubleBitmap-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">rendering</a> :: </p>
+</td>
+</tr>
+<tr>
+<td class="title"><table class="title-table" width="99%">
+<tr>
+<td width="25%" class="title2">unpublished </td>
+<td width="50%" class="title">interface XIeeeDoubleBitmap</td>
+<td width="*"/></tr>
+</table>
+</td>
+</tr>
+<tr>
+<td><dl>
+<dt><b>Base Interfaces</b></dt>
+<dd><pre style="font-family:monospace;"><strong>XIeeeDoubleBitmap</strong>
+&#x2517 <a href="XBitmap.html">XBitmap</a>
+   &#x2517 ::com::sun::star::uno::XInterface
+
+</pre></dd>
+<dd><a name/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="crosstitle">
+<tr>
+<td class="imsum_left"><a href="XBitmap.html">XBitmap</a></td>
+<td class="imsum_right"><dl>
+<dt>(referenced interface's summary:)</dt>
+<dd>This is a generic interface to a bitmap. </dd>
+</dl>
+</td>
+</tr>
+</table>
+</dd>
+</dl>
+</td>
+</tr>
+<tr>
+<td><dl>
+<dt><b>Description</b></dt>
+<dd>This is a specialized interface for bitmaps containing IEEE 
+doubles for their color components. 
+</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="#getData">getData</a></td>
+<td class="imsum_right">Query the raw data of this bitmap. 
+
+Query the raw data of this bitmap, in the format as defined by 
+getMemoryLayout(). With the given rectangle, a subset of the 
+whole bitmap can be queried. When querying subsets of the 
+bitmap, the same scanline padding takes place as when the 
+whole bitmap is requested. 
+
+Note that the bitmap memory layout might change for volatile 
+bitmaps. &nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#setData">setData</a></td>
+<td class="imsum_right">Set raw data of a bitmap. 
+
+Set raw data of a bitmap, in the format as defined by 
+getMemoryLayout(). With the given rectangle, a subset of the 
+bitmap can be changed. When setting subsets of the bitmap, the 
+same scanline padding takes place as when the whole bitmap is 
+changed. &nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#setPixel">setPixel</a></td>
+<td class="imsum_right">Set a single pixel of the bitmap with the given color 
+value. 
+
+When setting data on volatile bitmaps, always call isValid() 
+before, and retrieve a new memory layout via 
+getMemoryLayout(). At least under Windows, the memory layout 
+can change for the same bitmap, if the user e.g. switches the 
+screen resolution. Thus, this method will throw an 
+IllegalArgumentException, if the memory layout changed between 
+a call to getMemoryLayout() and setPixel(). 
+
+&nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#getPixel">getPixel</a></td>
+<td class="imsum_right">Get a single pixel of the bitmap, returning its color 
+value. 
+
+Note that the bitmap memory layout might change for volatile 
+bitmaps. &nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#getMemoryLayout">getMemoryLayout</a></td>
+<td class="imsum_right">Query the memory layout for this bitmap 
+
+Please note that for volatile bitmaps, the memory layout might 
+change between subsequent calls. 
+&nbsp;</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="getData" class="membertitle">getData</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">sequence&lt; double &gt;</td>
+</tr>
+<tr>
+<td valign="top"><b>getData</b>(</td>
+<td valign="top">[out] <a href="FloatingPointBitmapLayout.html">FloatingPointBitmapLayout</a></td>
+<td valign="bottom">&nbsp;bitmapLayout,</td>
+</tr>
+<tr>
+<td/><td valign="top">[in] ::com::sun::star::geometry::IntegerRectangle2D</td>
+<td valign="bottom">&nbsp;rect )</td>
+</tr>
+<tr>
+<td valign="top" align="right">raises( </td>
+<td valign="top" colspan="2">::com::sun::star::lang::IndexOutOfBoundsException,<br>
+<a href="VolatileContentDestroyedException.html">VolatileContentDestroyedException</a> );</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Query the raw data of this bitmap. 
+
+Query the raw data of this bitmap, in the format as defined by 
+getMemoryLayout(). With the given rectangle, a subset of the 
+whole bitmap can be queried. When querying subsets of the 
+bitmap, the same scanline padding takes place as when the 
+whole bitmap is requested. 
+
+Note that the bitmap memory layout might change for volatile 
+bitmaps. </dd>
+<dd><p>
+
+</dd>
+<dt><b>Parameter bitmapLayout</b></dt>
+<dd>The memory layout the returned data is in. 
+
+</dd>
+<dt><b>Parameter rect</b></dt>
+<dd>A rectangle, within the bounds of the bitmap, to retrieve the 
+contens from. 
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd>VolatileContentDestroyedException 
+if the bitmap is volatile, and the content has been destroyed by the system. 
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd>com::sun::star::lang::IndexOutOfBoundsException 
+if parts of the given rectangle are outside the permissible 
+bitmap area. 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="setData" class="membertitle">setData</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>setData</b>(</td>
+<td valign="top">[in] sequence&lt; double &gt;</td>
+<td valign="bottom">&nbsp;data,</td>
+</tr>
+<tr>
+<td/><td valign="top">[in] <a href="FloatingPointBitmapLayout.html">FloatingPointBitmapLayout</a></td>
+<td valign="bottom">&nbsp;bitmapLayout,</td>
+</tr>
+<tr>
+<td/><td valign="top">[in] ::com::sun::star::geometry::IntegerRectangle2D</td>
+<td valign="bottom">&nbsp;rect )</td>
+</tr>
+<tr>
+<td valign="top" align="right">raises( </td>
+<td valign="top" colspan="2">::com::sun::star::lang::IllegalArgumentException,<br>
+::com::sun::star::lang::IndexOutOfBoundsException );</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Set raw data of a bitmap. 
+
+Set raw data of a bitmap, in the format as defined by 
+getMemoryLayout(). With the given rectangle, a subset of the 
+bitmap can be changed. When setting subsets of the bitmap, the 
+same scanline padding takes place as when the whole bitmap is 
+changed. </dd>
+<dd><p>
+
+When setting data on volatile bitmaps, always call isValid() 
+before, and retrieve a new memory layout via 
+getMemoryLayout(). At least under Windows, the memory layout 
+can change for the same bitmap, if the user e.g. switches the 
+screen resolution. Thus, this method will throw an 
+IllegalArgumentException, if the memory layout changed between 
+a call to getMemoryLayout() and setData(). 
+
+</dd>
+<dt><b>Parameter data</b></dt>
+<dd>Data to set 
+
+</dd>
+<dt><b>Parameter bitmapLayout</b></dt>
+<dd>Layout of the data to set. Must match this bitmap's current 
+layout. 
+
+</dd>
+<dt><b>Parameter rect</b></dt>
+<dd>Destination rectangle, within the bounds of the bitmap, to set 
+the data in. 
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd>com::sun::star::lang::IndexOutOfBoundsException 
+if parts of the given rectangle are outside the permissible 
+bitmap area. 
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd>com::sun::star::lang::IllegalArgumentException 
+if the given memory layout does not match this bitmap's 
+layout, or if the given data sequence has too few or too much 
+elements. 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="setPixel" class="membertitle">setPixel</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>setPixel</b>(</td>
+<td valign="top">[in] sequence&lt; double &gt;</td>
+<td valign="bottom">&nbsp;color,</td>
+</tr>
+<tr>
+<td/><td valign="top">[in] <a href="FloatingPointBitmapLayout.html">FloatingPointBitmapLayout</a></td>
+<td valign="bottom">&nbsp;bitmapLayout,</td>
+</tr>
+<tr>
+<td/><td valign="top">[in] ::com::sun::star::geometry::IntegerPoint2D</td>
+<td valign="bottom">&nbsp;pos )</td>
+</tr>
+<tr>
+<td valign="top" align="right">raises( </td>
+<td valign="top" colspan="2">::com::sun::star::lang::IllegalArgumentException,<br>
+::com::sun::star::lang::IndexOutOfBoundsException );</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Set a single pixel of the bitmap with the given color 
+value. 
+
+When setting data on volatile bitmaps, always call isValid() 
+before, and retrieve a new memory layout via 
+getMemoryLayout(). At least under Windows, the memory layout 
+can change for the same bitmap, if the user e.g. switches the 
+screen resolution. Thus, this method will throw an 
+IllegalArgumentException, if the memory layout changed between 
+a call to getMemoryLayout() and setPixel(). 
+
+</dd>
+<dt><b>Parameter color</b></dt>
+<dd>The color value(s) to set 
+
+</dd>
+<dt><b>Parameter bitmapLayout</b></dt>
+<dd>Layout of the color elements to set. Must match this bitmap's 
+current layout. 
+
+</dd>
+<dt><b>Parameter pos</b></dt>
+<dd>Pixel position with the bounds of the bitmap to set. 
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd>com::sun::star::lang::IndexOutOfBoundsException 
+if the given point is outside the permissible bitmap area. 
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd>com::sun::star::lang::IllegalArgumentException 
+if the given memory layout does not match this bitmap's 
+layout, or if the given data sequence has too few or too much 
+elements. 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="getPixel" class="membertitle">getPixel</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">sequence&lt; double &gt;</td>
+</tr>
+<tr>
+<td valign="top"><b>getPixel</b>(</td>
+<td valign="top">[out] <a href="FloatingPointBitmapLayout.html">FloatingPointBitmapLayout</a></td>
+<td valign="bottom">&nbsp;bitmapLayout,</td>
+</tr>
+<tr>
+<td/><td valign="top">[in] ::com::sun::star::geometry::IntegerPoint2D</td>
+<td valign="bottom">&nbsp;pos )</td>
+</tr>
+<tr>
+<td valign="top" align="right">raises( </td>
+<td valign="top" colspan="2">::com::sun::star::lang::IndexOutOfBoundsException,<br>
+<a href="VolatileContentDestroyedException.html">VolatileContentDestroyedException</a> );</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Get a single pixel of the bitmap, returning its color 
+value. 
+
+Note that the bitmap memory layout might change for volatile 
+bitmaps. </dd>
+<dd><p>
+
+</dd>
+<dt><b>Parameter bitmapLayout</b></dt>
+<dd>The memory layout the returned data is in. 
+
+</dd>
+<dt><b>Parameter pos</b></dt>
+<dd>A position, within the bounds of the bitmap, to retrieve the 
+color from. 
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd>VolatileContentDestroyedException 
+if the bitmap is volatile, and the content has been destroyed by the system. 
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd>com::sun::star::lang::IndexOutOfBoundsException 
+if the given position is outside the permissible bitmap area. 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="getMemoryLayout" class="membertitle">getMemoryLayout</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="FloatingPointBitmapLayout.html">FloatingPointBitmapLayout</a></td>
+</tr>
+<tr>
+<td valign="top"><b>getMemoryLayout</b>();</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Query the memory layout for this bitmap 
+
+Please note that for volatile bitmaps, the memory layout might 
+change between subsequent calls. 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright &copy; 2003 Sun Microsystems, Inc.</p>
+
+</div> <!-- id="adc-idlref" -->
+</body>
+
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIeeeDoubleBitmap.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIeeeFloatBitmap-xref.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIeeeFloatBitmap-xref.html?rev=1206299&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIeeeFloatBitmap-xref.html (added)
+++ incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIeeeFloatBitmap-xref.html Fri Nov 25 20:06:37 2011
@@ -0,0 +1,55 @@
+<html>
+<head>
+<title>Uses of Interface XIeeeFloatBitmap-xref</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="navimainself">Use</td>
+<td class="navimainnone">Devguide</td>
+<td class="navimain"><a href="../../../../index-files/index-1.html" class="navimain">Index</a></td>
+</tr>
+</table>
+<hr>
+<table border="0" width="100%" cellpadding="5" cellspacing="3" class="title-table" style="margin-bottom:6pt;">
+<tr>
+<td class="title">uses of interface XIeeeFloatBitmap</td>
+</tr>
+<tr>
+<td><p><a href="XIeeeFloatBitmap.html"><b>back to interface XIeeeFloatBitmap</b></a><br>
+<br>
+
+Derived Interfaces<br>
+
+Synonym Typedefs<br>
+
+Services which Support this Interface<br>
+
+Singletons which Support this Interface<br>
+
+Uses as Return Type<br>
+
+Uses as Parameter<br>
+
+Uses as Data Type<br>
+
+References in Developers Guide<br>
+
+</p>
+</td>
+</tr>
+</table>
+<hr>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright &copy; 2003 Sun Microsystems, Inc.</p>
+
+</div> <!-- id="adc-idlref" -->
+</body>
+
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIeeeFloatBitmap-xref.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIeeeFloatBitmap.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIeeeFloatBitmap.html?rev=1206299&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIeeeFloatBitmap.html (added)
+++ incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIeeeFloatBitmap.html Fri Nov 25 20:06:37 2011
@@ -0,0 +1,445 @@
+<html>
+<head>
+<title>Interface XIeeeFloatBitmap</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="XIeeeFloatBitmap-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">rendering</a> :: </p>
+</td>
+</tr>
+<tr>
+<td class="title"><table class="title-table" width="99%">
+<tr>
+<td width="25%" class="title2">unpublished </td>
+<td width="50%" class="title">interface XIeeeFloatBitmap</td>
+<td width="*"/></tr>
+</table>
+</td>
+</tr>
+<tr>
+<td><dl>
+<dt><b>Base Interfaces</b></dt>
+<dd><pre style="font-family:monospace;"><strong>XIeeeFloatBitmap</strong>
+&#x2517 <a href="XBitmap.html">XBitmap</a>
+   &#x2517 ::com::sun::star::uno::XInterface
+
+</pre></dd>
+<dd><a name/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="crosstitle">
+<tr>
+<td class="imsum_left"><a href="XBitmap.html">XBitmap</a></td>
+<td class="imsum_right"><dl>
+<dt>(referenced interface's summary:)</dt>
+<dd>This is a generic interface to a bitmap. </dd>
+</dl>
+</td>
+</tr>
+</table>
+</dd>
+</dl>
+</td>
+</tr>
+<tr>
+<td><dl>
+<dt><b>Description</b></dt>
+<dd>Specialized interface for bitmaps containing IEEE floats as their 
+color components. 
+</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="#getData">getData</a></td>
+<td class="imsum_right">Query the raw data of this bitmap. 
+
+Query the raw data of this bitmap, in the format as defined by 
+getMemoryLayout(). With the given rectangle, a subset of the 
+whole bitmap can be queried. When querying subsets of the 
+bitmap, the same scanline padding takes place as when the 
+whole bitmap is requested. 
+
+Note that the bitmap memory layout might change for volatile 
+bitmaps. &nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#setData">setData</a></td>
+<td class="imsum_right">Set raw data of a bitmap. 
+
+Set raw data of a bitmap, in the format as defined by 
+getMemoryLayout(). With the given rectangle, a subset of the 
+bitmap can be changed. When setting subsets of the bitmap, the 
+same scanline padding takes place as when the whole bitmap is 
+changed. &nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#setPixel">setPixel</a></td>
+<td class="imsum_right">Set a single pixel of the bitmap with the given color 
+value. 
+
+When setting data on volatile bitmaps, always call isValid() 
+before, and retrieve a new memory layout via 
+getMemoryLayout(). At least under Windows, the memory layout 
+can change for the same bitmap, if the user e.g. switches the 
+screen resolution. Thus, this method will throw an 
+IllegalArgumentException, if the memory layout changed between 
+a call to getMemoryLayout() and setPixel(). 
+
+&nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#getPixel">getPixel</a></td>
+<td class="imsum_right">Get a single pixel of the bitmap, returning its color 
+value. 
+
+Note that the bitmap memory layout might change for volatile 
+bitmaps. &nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#getMemoryLayout">getMemoryLayout</a></td>
+<td class="imsum_right">Query the memory layout for this bitmap 
+
+Please note that for volatile bitmaps, the memory layout might 
+change between subsequent calls. 
+&nbsp;</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="getData" class="membertitle">getData</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">sequence&lt; float &gt;</td>
+</tr>
+<tr>
+<td valign="top"><b>getData</b>(</td>
+<td valign="top">[out] <a href="FloatingPointBitmapLayout.html">FloatingPointBitmapLayout</a></td>
+<td valign="bottom">&nbsp;bitmapLayout,</td>
+</tr>
+<tr>
+<td/><td valign="top">[in] ::com::sun::star::geometry::IntegerRectangle2D</td>
+<td valign="bottom">&nbsp;rect )</td>
+</tr>
+<tr>
+<td valign="top" align="right">raises( </td>
+<td valign="top" colspan="2">::com::sun::star::lang::IndexOutOfBoundsException,<br>
+<a href="VolatileContentDestroyedException.html">VolatileContentDestroyedException</a> );</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Query the raw data of this bitmap. 
+
+Query the raw data of this bitmap, in the format as defined by 
+getMemoryLayout(). With the given rectangle, a subset of the 
+whole bitmap can be queried. When querying subsets of the 
+bitmap, the same scanline padding takes place as when the 
+whole bitmap is requested. 
+
+Note that the bitmap memory layout might change for volatile 
+bitmaps. </dd>
+<dd><p>
+
+</dd>
+<dt><b>Parameter bitmapLayout</b></dt>
+<dd>The memory layout the returned data is in. 
+
+</dd>
+<dt><b>Parameter rect</b></dt>
+<dd>A rectangle, within the bounds of the bitmap, to retrieve the 
+contens from. 
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd>VolatileContentDestroyedException 
+if the bitmap is volatile, and the content has been destroyed by the system. 
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd>com::sun::star::lang::IndexOutOfBoundsException 
+if parts of the given rectangle are outside the permissible 
+bitmap area. 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="setData" class="membertitle">setData</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>setData</b>(</td>
+<td valign="top">[in] sequence&lt; float &gt;</td>
+<td valign="bottom">&nbsp;data,</td>
+</tr>
+<tr>
+<td/><td valign="top">[in] <a href="FloatingPointBitmapLayout.html">FloatingPointBitmapLayout</a></td>
+<td valign="bottom">&nbsp;bitmapLayout,</td>
+</tr>
+<tr>
+<td/><td valign="top">[in] ::com::sun::star::geometry::IntegerRectangle2D</td>
+<td valign="bottom">&nbsp;rect )</td>
+</tr>
+<tr>
+<td valign="top" align="right">raises( </td>
+<td valign="top" colspan="2">::com::sun::star::lang::IllegalArgumentException,<br>
+::com::sun::star::lang::IndexOutOfBoundsException );</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Set raw data of a bitmap. 
+
+Set raw data of a bitmap, in the format as defined by 
+getMemoryLayout(). With the given rectangle, a subset of the 
+bitmap can be changed. When setting subsets of the bitmap, the 
+same scanline padding takes place as when the whole bitmap is 
+changed. </dd>
+<dd><p>
+
+When setting data on volatile bitmaps, always call isValid() 
+before, and retrieve a new memory layout via 
+getMemoryLayout(). At least under Windows, the memory layout 
+can change for the same bitmap, if the user e.g. switches the 
+screen resolution. Thus, this method will throw an 
+IllegalArgumentException, if the memory layout changed between 
+a call to getMemoryLayout() and setData(). 
+
+</dd>
+<dt><b>Parameter data</b></dt>
+<dd>Data to set 
+
+</dd>
+<dt><b>Parameter bitmapLayout</b></dt>
+<dd>Layout of the data to set. Must match this bitmap's current 
+layout. 
+
+</dd>
+<dt><b>Parameter rect</b></dt>
+<dd>Destination rectangle, within the bounds of the bitmap, to set 
+the data in. 
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd>com::sun::star::lang::IndexOutOfBoundsException 
+if parts of the given rectangle are outside the permissible 
+bitmap area. 
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd>com::sun::star::lang::IllegalArgumentException 
+if the given memory layout does not match this bitmap's 
+layout, or if the given data sequence has too few or too much 
+elements. 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="setPixel" class="membertitle">setPixel</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>setPixel</b>(</td>
+<td valign="top">[in] sequence&lt; float &gt;</td>
+<td valign="bottom">&nbsp;color,</td>
+</tr>
+<tr>
+<td/><td valign="top">[in] <a href="FloatingPointBitmapLayout.html">FloatingPointBitmapLayout</a></td>
+<td valign="bottom">&nbsp;bitmapLayout,</td>
+</tr>
+<tr>
+<td/><td valign="top">[in] ::com::sun::star::geometry::IntegerPoint2D</td>
+<td valign="bottom">&nbsp;pos )</td>
+</tr>
+<tr>
+<td valign="top" align="right">raises( </td>
+<td valign="top" colspan="2">::com::sun::star::lang::IllegalArgumentException,<br>
+::com::sun::star::lang::IndexOutOfBoundsException );</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Set a single pixel of the bitmap with the given color 
+value. 
+
+When setting data on volatile bitmaps, always call isValid() 
+before, and retrieve a new memory layout via 
+getMemoryLayout(). At least under Windows, the memory layout 
+can change for the same bitmap, if the user e.g. switches the 
+screen resolution. Thus, this method will throw an 
+IllegalArgumentException, if the memory layout changed between 
+a call to getMemoryLayout() and setPixel(). 
+
+</dd>
+<dt><b>Parameter color</b></dt>
+<dd>The color value(s) to set 
+
+</dd>
+<dt><b>Parameter bitmapLayout</b></dt>
+<dd>Layout of the color elements to set. Must match this bitmap's 
+current layout. 
+
+</dd>
+<dt><b>Parameter pos</b></dt>
+<dd>Pixel position with the bounds of the bitmap to set. 
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd>com::sun::star::lang::IndexOutOfBoundsException 
+if the given point is outside the permissible bitmap area. 
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd>com::sun::star::lang::IllegalArgumentException 
+if the given memory layout does not match this bitmap's 
+layout, or if the given data sequence has too few or too much 
+elements. 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="getPixel" class="membertitle">getPixel</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">sequence&lt; float &gt;</td>
+</tr>
+<tr>
+<td valign="top"><b>getPixel</b>(</td>
+<td valign="top">[out] <a href="FloatingPointBitmapLayout.html">FloatingPointBitmapLayout</a></td>
+<td valign="bottom">&nbsp;bitmapLayout,</td>
+</tr>
+<tr>
+<td/><td valign="top">[in] ::com::sun::star::geometry::IntegerPoint2D</td>
+<td valign="bottom">&nbsp;pos )</td>
+</tr>
+<tr>
+<td valign="top" align="right">raises( </td>
+<td valign="top" colspan="2">::com::sun::star::lang::IndexOutOfBoundsException,<br>
+<a href="VolatileContentDestroyedException.html">VolatileContentDestroyedException</a> );</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Get a single pixel of the bitmap, returning its color 
+value. 
+
+Note that the bitmap memory layout might change for volatile 
+bitmaps. </dd>
+<dd><p>
+
+</dd>
+<dt><b>Parameter bitmapLayout</b></dt>
+<dd>The memory layout the returned data is in. 
+
+</dd>
+<dt><b>Parameter pos</b></dt>
+<dd>A position, within the bounds of the bitmap, to retrieve the 
+color from. 
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd>VolatileContentDestroyedException 
+if the bitmap is volatile, and the content has been destroyed by the system. 
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd>com::sun::star::lang::IndexOutOfBoundsException 
+if the given position is outside the permissible bitmap area. 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="getMemoryLayout" class="membertitle">getMemoryLayout</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="FloatingPointBitmapLayout.html">FloatingPointBitmapLayout</a></td>
+</tr>
+<tr>
+<td valign="top"><b>getMemoryLayout</b>();</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Query the memory layout for this bitmap 
+
+Please note that for volatile bitmaps, the memory layout might 
+change between subsequent calls. 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright &copy; 2003 Sun Microsystems, Inc.</p>
+
+</div> <!-- id="adc-idlref" -->
+</body>
+
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIeeeFloatBitmap.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIntegerBitmap-xref.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIntegerBitmap-xref.html?rev=1206299&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIntegerBitmap-xref.html (added)
+++ incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIntegerBitmap-xref.html Fri Nov 25 20:06:37 2011
@@ -0,0 +1,55 @@
+<html>
+<head>
+<title>Uses of Interface XIntegerBitmap-xref</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="navimainself">Use</td>
+<td class="navimainnone">Devguide</td>
+<td class="navimain"><a href="../../../../index-files/index-1.html" class="navimain">Index</a></td>
+</tr>
+</table>
+<hr>
+<table border="0" width="100%" cellpadding="5" cellspacing="3" class="title-table" style="margin-bottom:6pt;">
+<tr>
+<td class="title">uses of interface XIntegerBitmap</td>
+</tr>
+<tr>
+<td><p><a href="XIntegerBitmap.html"><b>back to interface XIntegerBitmap</b></a><br>
+<br>
+
+Derived Interfaces<br>
+
+Synonym Typedefs<br>
+
+Services which Support this Interface<br>
+
+Singletons which Support this Interface<br>
+
+Uses as Return Type<br>
+
+Uses as Parameter<br>
+
+Uses as Data Type<br>
+
+References in Developers Guide<br>
+
+</p>
+</td>
+</tr>
+</table>
+<hr>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright &copy; 2003 Sun Microsystems, Inc.</p>
+
+</div> <!-- id="adc-idlref" -->
+</body>
+
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIntegerBitmap-xref.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIntegerBitmap.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIntegerBitmap.html?rev=1206299&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIntegerBitmap.html (added)
+++ incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIntegerBitmap.html Fri Nov 25 20:06:37 2011
@@ -0,0 +1,487 @@
+<html>
+<head>
+<title>Interface XIntegerBitmap</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="XIntegerBitmap-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">rendering</a> :: </p>
+</td>
+</tr>
+<tr>
+<td class="title"><table class="title-table" width="99%">
+<tr>
+<td width="25%" class="title2">unpublished </td>
+<td width="50%" class="title">interface XIntegerBitmap</td>
+<td width="*"/></tr>
+</table>
+</td>
+</tr>
+<tr>
+<td><dl>
+<dt><b>Base Interfaces</b></dt>
+<dd><pre style="font-family:monospace;"><strong>XIntegerBitmap</strong>
+&#x2517 <a href="XBitmap.html">XBitmap</a>
+   &#x2517 ::com::sun::star::uno::XInterface
+
+</pre></dd>
+<dd><a name/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="crosstitle">
+<tr>
+<td class="imsum_left"><a href="XBitmap.html">XBitmap</a></td>
+<td class="imsum_right"><dl>
+<dt>(referenced interface's summary:)</dt>
+<dd>This is a generic interface to a bitmap. </dd>
+</dl>
+</td>
+</tr>
+</table>
+</dd>
+</dl>
+</td>
+</tr>
+<tr>
+<td><dl>
+<dt><b>Description</b></dt>
+<dd>This is a specialized interface for bitmaps having integer color 
+channels. 
+</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="#getData">getData</a></td>
+<td class="imsum_right">Query the raw data of this bitmap. &nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#setData">setData</a></td>
+<td class="imsum_right">Set raw data of a bitmap. 
+
+Set raw data of a bitmap, in the format as defined by 
+getMemoryLayout(). With the given rectangle, a subset of the 
+bitmap can be changed. If the internal data format's pixel are 
+not integer multiples of bytes (i.e. if one pixel occupies 
+less than a byte), the leftover content of the bytes at the 
+right of each scanline is ignored and left unchanged in the 
+bitmap. When setting subsets of the bitmap, the same scanline 
+padding takes place as when the whole bitmap is changed. &nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#setPixel">setPixel</a></td>
+<td class="imsum_right">Set a single pixel of the bitmap with the given color 
+value. 
+
+If the internal data format's pixel are not integer multiples 
+of bytes (i.e. if one pixel occupies less than a byte), the 
+color value is expected in the least significant bits of the 
+single byte given as the color. &nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#getPixel">getPixel</a></td>
+<td class="imsum_right">Get a single pixel of the bitmap, returning its color 
+value. 
+
+If the internal data format's pixel are not integer multiples 
+of bytes (i.e. if one pixel occupies less than a byte), the 
+color value is returned in the least significant bits of the 
+single byte returned as the color. 
+
+Note that the bitmap memory layout might change for volatile 
+bitmaps. &nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#getPalette">getPalette</a></td>
+<td class="imsum_right">Query the associated palette for this bitmap. 
+
+Returns empty interface or interface with empty palette for 
+non-paletted bitmaps. 
+&nbsp;</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#getMemoryLayout">getMemoryLayout</a></td>
+<td class="imsum_right">Query the memory layout for this bitmap. &nbsp;</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="getData" class="membertitle">getData</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">sequence&lt; byte &gt;</td>
+</tr>
+<tr>
+<td valign="top"><b>getData</b>(</td>
+<td valign="top">[out] <a href="IntegerBitmapLayout.html">IntegerBitmapLayout</a></td>
+<td valign="bottom">&nbsp;bitmapLayout,</td>
+</tr>
+<tr>
+<td/><td valign="top">[in] ::com::sun::star::geometry::IntegerRectangle2D</td>
+<td valign="bottom">&nbsp;rect )</td>
+</tr>
+<tr>
+<td valign="top" align="right">raises( </td>
+<td valign="top" colspan="2">::com::sun::star::lang::IndexOutOfBoundsException,<br>
+<a href="VolatileContentDestroyedException.html">VolatileContentDestroyedException</a> );</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Query the raw data of this bitmap. </dd>
+<dd><p>
+
+Query the raw data of this bitmap, in the format as defined by 
+getMemoryLayout(). With the given rectangle, a subset of the 
+whole bitmap can be queried. If the internal data format's 
+pixel are not integer multiples of bytes (i.e. if one pixel 
+occupies less than a byte), the leftover content of the bytes 
+at the right of each scanline is filled with zero. When 
+querying subsets of the bitmap, the same scanline padding 
+takes place as when the whole bitmap is requested. <p>
+
+Note that the bitmap memory layout might change for volatile 
+bitmaps. <p>
+
+</dd>
+<dt><b>Parameter bitmapLayout</b></dt>
+<dd>The memory layout the returned data is in. 
+
+</dd>
+<dt><b>Parameter rect</b></dt>
+<dd>A rectangle, within the bounds of the bitmap, to retrieve the 
+contens from. 
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd>VolatileContentDestroyedException 
+if the bitmap is volatile, and the content has been destroyed by the system. 
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd>com::sun::star::lang::IndexOutOfBoundsException 
+if parts of the given rectangle are outside the permissible 
+bitmap area. 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="setData" class="membertitle">setData</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>setData</b>(</td>
+<td valign="top">[in] sequence&lt; byte &gt;</td>
+<td valign="bottom">&nbsp;data,</td>
+</tr>
+<tr>
+<td/><td valign="top">[in] <a href="IntegerBitmapLayout.html">IntegerBitmapLayout</a></td>
+<td valign="bottom">&nbsp;bitmapLayout,</td>
+</tr>
+<tr>
+<td/><td valign="top">[in] ::com::sun::star::geometry::IntegerRectangle2D</td>
+<td valign="bottom">&nbsp;rect )</td>
+</tr>
+<tr>
+<td valign="top" align="right">raises( </td>
+<td valign="top" colspan="2">::com::sun::star::lang::IllegalArgumentException,<br>
+::com::sun::star::lang::IndexOutOfBoundsException );</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Set raw data of a bitmap. 
+
+Set raw data of a bitmap, in the format as defined by 
+getMemoryLayout(). With the given rectangle, a subset of the 
+bitmap can be changed. If the internal data format's pixel are 
+not integer multiples of bytes (i.e. if one pixel occupies 
+less than a byte), the leftover content of the bytes at the 
+right of each scanline is ignored and left unchanged in the 
+bitmap. When setting subsets of the bitmap, the same scanline 
+padding takes place as when the whole bitmap is changed. </dd>
+<dd><p>
+
+When setting data on volatile bitmaps, always call isValid() 
+before, and retrieve a new memory layout via 
+getMemoryLayout(). At least under Windows, the memory layout 
+can change for the same bitmap, if the user e.g. switches the 
+screen resolution. Thus, this method will throw an 
+IllegalArgumentException, if the memory layout changed between 
+a call to getMemoryLayout() and setData(). 
+
+</dd>
+<dt><b>Parameter data</b></dt>
+<dd>Data to set 
+
+</dd>
+<dt><b>Parameter bitmapLayout</b></dt>
+<dd>Layout of the data to set. Must match this bitmap's current 
+layout. 
+
+</dd>
+<dt><b>Parameter rect</b></dt>
+<dd>Destination rectangle, within the bounds of the bitmap, to set 
+the data in. 
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd>com::sun::star::lang::IndexOutOfBoundsException 
+if parts of the given rectangle are outside the permissible 
+bitmap area. 
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd>com::sun::star::lang::IllegalArgumentException 
+if the given memory layout does not match this bitmap's 
+layout, or if the given data sequence has too few or too much 
+elements. 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="setPixel" class="membertitle">setPixel</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>setPixel</b>(</td>
+<td valign="top">[in] sequence&lt; byte &gt;</td>
+<td valign="bottom">&nbsp;color,</td>
+</tr>
+<tr>
+<td/><td valign="top">[in] <a href="IntegerBitmapLayout.html">IntegerBitmapLayout</a></td>
+<td valign="bottom">&nbsp;bitmapLayout,</td>
+</tr>
+<tr>
+<td/><td valign="top">[in] ::com::sun::star::geometry::IntegerPoint2D</td>
+<td valign="bottom">&nbsp;pos )</td>
+</tr>
+<tr>
+<td valign="top" align="right">raises( </td>
+<td valign="top" colspan="2">::com::sun::star::lang::IllegalArgumentException,<br>
+::com::sun::star::lang::IndexOutOfBoundsException );</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Set a single pixel of the bitmap with the given color 
+value. 
+
+If the internal data format's pixel are not integer multiples 
+of bytes (i.e. if one pixel occupies less than a byte), the 
+color value is expected in the least significant bits of the 
+single byte given as the color. </dd>
+<dd><p>
+
+When setting data on volatile bitmaps, always call isValid() 
+before, and retrieve a new memory layout via 
+getMemoryLayout(). At least under Windows, the memory layout 
+can change for the same bitmap, if the user e.g. switches the 
+screen resolution. Thus, this method will throw an 
+IllegalArgumentException, if the memory layout changed between 
+a call to getMemoryLayout() and setPixel(). 
+
+</dd>
+<dt><b>Parameter color</b></dt>
+<dd>The color value(s) to set 
+
+</dd>
+<dt><b>Parameter bitmapLayout</b></dt>
+<dd>Layout of the color elements to set. Must match this bitmap's 
+current layout. 
+
+</dd>
+<dt><b>Parameter pos</b></dt>
+<dd>Pixel position with the bounds of the bitmap to set. 
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd>com::sun::star::lang::IndexOutOfBoundsException 
+if the given point is outside the permissible bitmap area. 
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd>com::sun::star::lang::IllegalArgumentException 
+if the given memory layout does not match this bitmap's 
+layout, or if the given data sequence has too few or too much 
+elements. 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="getPixel" class="membertitle">getPixel</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">sequence&lt; byte &gt;</td>
+</tr>
+<tr>
+<td valign="top"><b>getPixel</b>(</td>
+<td valign="top">[out] <a href="IntegerBitmapLayout.html">IntegerBitmapLayout</a></td>
+<td valign="bottom">&nbsp;bitmapLayout,</td>
+</tr>
+<tr>
+<td/><td valign="top">[in] ::com::sun::star::geometry::IntegerPoint2D</td>
+<td valign="bottom">&nbsp;pos )</td>
+</tr>
+<tr>
+<td valign="top" align="right">raises( </td>
+<td valign="top" colspan="2">::com::sun::star::lang::IndexOutOfBoundsException,<br>
+<a href="VolatileContentDestroyedException.html">VolatileContentDestroyedException</a> );</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Get a single pixel of the bitmap, returning its color 
+value. 
+
+If the internal data format's pixel are not integer multiples 
+of bytes (i.e. if one pixel occupies less than a byte), the 
+color value is returned in the least significant bits of the 
+single byte returned as the color. 
+
+Note that the bitmap memory layout might change for volatile 
+bitmaps. </dd>
+<dd><p>
+
+</dd>
+<dt><b>Parameter bitmapLayout</b></dt>
+<dd>The memory layout the returned data is in. 
+
+</dd>
+<dt><b>Parameter pos</b></dt>
+<dd>A position, within the bounds of the bitmap, to retrieve the 
+color from. 
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd>VolatileContentDestroyedException 
+if the bitmap is volatile, and the content has been destroyed by the system. 
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd>com::sun::star::lang::IndexOutOfBoundsException 
+if the given position is outside the permissible bitmap area. 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="getPalette" class="membertitle">getPalette</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="XBitmapPalette.html">XBitmapPalette</a></td>
+</tr>
+<tr>
+<td valign="top"><b>getPalette</b>();</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Query the associated palette for this bitmap. 
+
+Returns empty interface or interface with empty palette for 
+non-paletted bitmaps. 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="getMemoryLayout" class="membertitle">getMemoryLayout</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="IntegerBitmapLayout.html">IntegerBitmapLayout</a></td>
+</tr>
+<tr>
+<td valign="top"><b>getMemoryLayout</b>();</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>Query the memory layout for this bitmap. </dd>
+<dd><p>
+
+Please note that for volatile bitmaps, the memory layout might 
+change between subsequent calls. 
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright &copy; 2003 Sun Microsystems, Inc.</p>
+
+</div> <!-- id="adc-idlref" -->
+</body>
+
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/gsl/canvas/api/rendering/XIntegerBitmap.html
------------------------------------------------------------------------------
    svn:eol-style = native



Mime
View raw message