Mercurial Mercurial > oss > FCL > sftools > depl > docscontent / diff
summary | shortlog | changelog | graph | tags | bookmarks | branches | files | changeset | file | latest | revisions | annotate | diff | comparison | raw | help
Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Symbian3/PDK/Source/GUID-DBEAD516-5DD4-5E33-B6DA-657C1AE60C4B.dita
changeset 12 80ef3a206772
parent 9 59758314f811
child 14 578be2adaf3e 
--- a/Symbian3/PDK/Source/GUID-DBEAD516-5DD4-5E33-B6DA-657C1AE60C4B.dita	Fri Jul 02 12:51:36 2010 +0100
+++ b/Symbian3/PDK/Source/GUID-DBEAD516-5DD4-5E33-B6DA-657C1AE60C4B.dita	Fri Jul 16 17:23:46 2010 +0100
@@ -55,10 +55,10 @@
 <tbody>
 <row>
 <entry><fig id="GUID-C7D88A4C-B5A0-5A1B-8710-188DC398B6CB">
-<image href="GUID-F127644A-6072-52CA-9B17-E9DDEA784BE0_d0e379843_href.png" placement="inline"/>
+<image href="GUID-F127644A-6072-52CA-9B17-E9DDEA784BE0_d0e385696_href.png" placement="inline"/>
 </fig> </entry>
 <entry><fig id="GUID-F244E871-48C7-548E-AF69-43D4265F9C48">
-<image href="GUID-9173EEBA-CC84-51D9-9C8D-A75F7F494D62_d0e379850_href.png" placement="inline"/>
+<image href="GUID-9173EEBA-CC84-51D9-9C8D-A75F7F494D62_d0e385703_href.png" placement="inline"/>
 </fig> </entry>
 </row>
 </tbody>
@@ -100,7 +100,7 @@
 </ol> </section>
 <section id="GUID-CD820F5C-01F7-427F-8FFC-675CDE48F1BD"><title>Interaction between the two layers</title> <p>This section
 shows the main interactions between the two layers: </p> <p><b>1</b> </p> <fig id="GUID-BC82D3E5-C190-57F4-AAC4-38532E2225E9">
-<image href="GUID-4FDD1F7B-1A4E-5389-A0A4-22727CD42B5B_d0e379956_href.png" placement="inline"/>
+<image href="GUID-4FDD1F7B-1A4E-5389-A0A4-22727CD42B5B_d0e385809_href.png" placement="inline"/>
 </fig> <p>When the device is started, the platform independent layer calls
 the function <codeph>DoCreate()</codeph>. This is where the power handler
 should be registered, interrupts bound and any other initialisation should
@@ -111,12 +111,12 @@
 scheduled to run when the pen is lifted. This DFC is scheduled in the platform
 specific layer. </p> <p>See also <xref href="GUID-AF71FDC2-A8CC-5035-91FE-36212844BC07.dita#GUID-AF71FDC2-A8CC-5035-91FE-36212844BC07/GUID-1A1194A0-DF74-59E7-B3AD-FD87D501F00F">Step
 4 - implement DDigitiser::WaitForPenDown()</xref>. </p> <p><b>2</b> </p> <fig id="GUID-3C50B57F-46A9-5CF0-94BB-50E63837D2CB">
-<image href="GUID-AE53C15E-0C0F-5726-BBA4-E7DCDA7F48B4_d0e379991_href.png" placement="inline"/>
+<image href="GUID-AE53C15E-0C0F-5726-BBA4-E7DCDA7F48B4_d0e385844_href.png" placement="inline"/>
 </fig> <p>The platform specific layer calls <codeph>RawSampleValid()</codeph> when
 it has a group of digitizer coordinates ready to be processed by the platform
 independent layer. This is called in the context of a DFC thread, the DFC
 being queued when the digitizer interrupt is fired. </p> <p><b>3</b> </p> <fig id="GUID-AAEC4068-6743-5E50-906D-AE05622A0627">
-<image href="GUID-DE7BD5C8-9966-5D5E-B81F-D57EA9FBA451_d0e380007_href.png" placement="inline"/>
+<image href="GUID-DE7BD5C8-9966-5D5E-B81F-D57EA9FBA451_d0e385860_href.png" placement="inline"/>
 </fig> <p>The platform independent layer calls <codeph>WaitForPenUp()</codeph> to
 request another sample from the hardware. This is declared as pure virtual
 in the <xref href="GUID-2EDAF642-2399-3594-986A-5E8A5EEA01B9.dita"><apiname>DDigitiser</apiname></xref> class and is implemented in the platform
@@ -124,7 +124,7 @@
 has processed a group of raw samples while the pen is down, and also tells
 the platform specific layer that the buffers in the platform independent layer
 can be re-used. </p> <p><b>4</b> </p> <fig id="GUID-5C3344EC-B07F-5D02-A107-7F4BB381EB55">
-<image href="GUID-C8450E58-A603-5CF8-993E-053C990DDA19_d0e380027_href.png" placement="inline"/>
+<image href="GUID-C8450E58-A603-5CF8-993E-053C990DDA19_d0e385880_href.png" placement="inline"/>
 </fig> <p>The platform independent layer calls <codeph>WaitForPenUpDebounce()</codeph> if
 a group of collected samples is not good enough. This is declared as pure
 virtual in the <xref href="GUID-2EDAF642-2399-3594-986A-5E8A5EEA01B9.dita"><apiname>DDigitiser</apiname></xref> class and is implemented in the
@@ -132,18 +132,18 @@
 layer has processed a group of raw samples while the pen is down and also
 tells the platform specific layer that the buffers in the platform independent
 layer can be re-used. </p> <p><b>5</b> </p> <fig id="GUID-CAF3646F-0078-5F25-94A8-B03A42B132BC">
-<image href="GUID-465D1450-B1EF-568B-B518-34ACE8C1697C_d0e380047_href.png" placement="inline"/>
+<image href="GUID-465D1450-B1EF-568B-B518-34ACE8C1697C_d0e385900_href.png" placement="inline"/>
 </fig> <p>When the pen is lifted, the platform specific layer calls <codeph>PenUp()</codeph> in
 the platform independent layer, which then changes its internal state, issues
 a pen up event to the device, and then calls <codeph>WaitForPenDown()</codeph> in
 the platform specific layer. </p> <p><b>6</b> </p> <fig id="GUID-77BBAF4E-D737-54CF-B67C-292D5ABD5CB3">
-<image href="GUID-DB0EDBC2-8204-59F3-9029-EBBCE04A9E3C_d0e380066_href.png" placement="inline"/>
+<image href="GUID-DB0EDBC2-8204-59F3-9029-EBBCE04A9E3C_d0e385919_href.png" placement="inline"/>
 </fig> <p>The platform independent layer calls <codeph>DigitiserOn()</codeph> when
 the device is turned on, or it may be called from the HAL. The function, implemented
 in the platform specific layer, and turns the hardware on if it is not already
 on. See also <xref href="GUID-AF71FDC2-A8CC-5035-91FE-36212844BC07.dita#GUID-AF71FDC2-A8CC-5035-91FE-36212844BC07/GUID-A4B43E01-9638-5967-8EFA-0AABA33189EA">Step
 3 - implement power on behaviour</xref>. </p> <p><b>7</b> </p> <fig id="GUID-481F038C-2C5D-5D95-88A3-62F54EEDA713">
-<image href="GUID-2622DE31-AA12-5FAD-86FB-B13259EFC6D9_d0e380085_href.png" placement="inline"/>
+<image href="GUID-2622DE31-AA12-5FAD-86FB-B13259EFC6D9_d0e385938_href.png" placement="inline"/>
 </fig> <p> <codeph>DigitiserOff()</codeph> turns the digitizer off, and may
 be called as a result of a power transition, or it may be called from the
 HAL. If it is called from the Power Manager, the digitizer may already be
@@ -151,7 +151,7 @@
 convert digitizer coordinates to and from screen coordinates. Both are declared
 as pure virtual in the <xref href="GUID-2EDAF642-2399-3594-986A-5E8A5EEA01B9.dita"><apiname>DDigitiser</apiname></xref> class and need to be
 implemented in the platform specific layer. </p> <p><b>9</b> </p> <fig id="GUID-500D1D6B-85AE-5C1C-8F34-95036A6B9D82">
-<image href="GUID-3F0053A7-6EE2-5B59-81C2-27EC3CC7820A_d0e380122_href.png" placement="inline"/>
+<image href="GUID-3F0053A7-6EE2-5B59-81C2-27EC3CC7820A_d0e385975_href.png" placement="inline"/>
 </fig> <p>The platform independent layer provides the <xref href="GUID-9AE254D4-AA60-579E-8D9D-F2797106A413.dita#GUID-9AE254D4-AA60-579E-8D9D-F2797106A413/GUID-1B59A40C-D023-5555-8E5E-DF18D653D321">HAL handler</xref> for the <xref href="GUID-E22F7F41-C578-36B4-A7AB-AE0AEF520A69.dita"><apiname>EHalGroupDigitiser</apiname></xref>  <xref href="GUID-9AE254D4-AA60-579E-8D9D-F2797106A413.dita#GUID-9AE254D4-AA60-579E-8D9D-F2797106A413/GUID-366CC4B8-C6BD-5DCC-B55D-6D87CD5C8E64">HAL groups and function-ids</xref>. This is <codeph>DDigitiser::HalFunction()</codeph>.
 It delegates the handling of 5 of the individual behaviours, as represented
 by the <xref href="GUID-86A737D5-0602-3DB3-9CFF-764C80A8D468.dita"><apiname>TDigitiserHalFunction</apiname></xref> function-ids, to the following
FCL/sftools/depl/docscontent