Unit TFT Framebuffer - Revision history

Ultibo at 05:08, 23 November 2022

2022-11-23T05:08:15Z

Ultibo at 05:04, 31 August 2021

2021-08-31T05:04:04Z

Ultibo at 06:45, 15 June 2021

2021-06-15T06:45:50Z

Ultibo at 06:08, 20 April 2018

2018-04-20T06:08:50Z

Ultibo at 02:06, 15 April 2018

2018-04-15T02:06:34Z

@@ Line 218: / Line 218: @@
 ! Note
 | Not intended to be called directly by applications, use FramebufferDeviceCommit instead.
 |-
 |}

@@ Line 5: / Line 5: @@
 ----
-'''Ultibo TFT Framebuffer driver library unit'''
+'''Ultibo TFT Framebuffer Driver Library unit'''
 This is a generic framebuffer device support unit for SPI based TFT screens using common chipsets.

@@ Line 75: / Line 75: @@
 {| class="wikitable" style="font-size: 14px; text-align: left; width: 100%; height: 50px;"
 |-
-| <code>TTFTFramebufferWriteMemory = function(Framebuffer:PTFTFramebuffer; Address,Size:LongWord):LongWord;</code>
+| <code>TTFTFramebufferWriteMemory = function(Framebuffer:PTFTFramebuffer; Address:PtrUInt; Size:LongWord):LongWord;</code>
 | style="width: 40%;"|
 |-
@@ Line 211: / Line 211: @@
 <br />
 <div class="toccolours mw-collapsible mw-collapsed" style="border: 1; font-family: arial; padding-top: 0px; padding-bottom: 15px;">
-<pre style="border: 0; padding-bottom:0px;">function TFTFramebufferCommit(Framebuffer:PFramebufferDevice; Address,Size,Flags:LongWord):LongWord;</pre>
+<pre style="border: 0; padding-bottom:0px;">function TFTFramebufferCommit(Framebuffer:PFramebufferDevice; Address:PtrUInt; Size,Flags:LongWord):LongWord;</pre>
 <div style="font-size: 14px; padding-left: 12px;">'''Description:''' Implementation of FramebufferDeviceCommit API for TFT Framebuffer</div>
 <div class="mw-collapsible-content" style="text-align: left; padding-left: 5px;">

@@ Line 179: / Line 179: @@
 {| class="wikitable" style="font-size: 14px; background: white;"
 |-
-! '''Note'''
+! Note
-| Not intended to be called directly by applications, use FramebufferDeviceAllocate instead
+| Not intended to be called directly by applications, use FramebufferDeviceAllocate instead.
 |-
 |}
@@ Line 191: / Line 191: @@
 {| class="wikitable" style="font-size: 14px; background: white;"
 |-
-! '''Note'''
+! Note
-| Not intended to be called directly by applications, use FramebufferDeviceRelease instead
+| Not intended to be called directly by applications, use FramebufferDeviceRelease instead.
 |-
 |}
@@ Line 203: / Line 203: @@
 {| class="wikitable" style="font-size: 14px; background: white;"
 |-
-! '''Note'''
+! Note
-| Not intended to be called directly by applications, use FramebufferDeviceMark instead. Marks full lines only, X and Width are ignored for TFT Framebuffer.
+| Not intended to be called directly by applications, use FramebufferDeviceMark instead.
 |-
 |}
@@ Line 215: / Line 216: @@
 {| class="wikitable" style="font-size: 14px; background: white;"
 |-
-! '''Note'''
+! Note
-| Not intended to be called directly by applications, use FramebufferDeviceCommit instead
+| Not intended to be called directly by applications, use FramebufferDeviceCommit instead.
 |-
 |}
@@ Line 227: / Line 228: @@
 {| class="wikitable" style="font-size: 14px; background: white;"
 |-
-! '''Note'''
+! Note
-| Not intended to be called directly by applications, use FramebufferDeviceSetProperties instead
+| Not intended to be called directly by applications, use FramebufferDeviceSetProperties instead.
 |-
 |}
@@ Line 239: / Line 240: @@
 {| class="wikitable" style="font-size: 14px; background: white;"
 |-
-! '''Note'''
+! Note
 | Not intended to be called directly by applications
 |-

@@ Line 9: / Line 9: @@
 This is a generic framebuffer device support unit for SPI based TFT screens using common chipsets.
-This unit implements the shared functionality that is common to all devices and provides a set of functions that device specific drivers must implement. For each supported device a driver unit is
+This unit implements the shared functionality that is common to all devices and provides a set of functions that device specific drivers must implement. For each supported device a driver unit is required that implements the SPI communications to initialize the device, setup resolution and color depth as well as refreshing the framebuffer data to the device memory on change.
 required that implements the SPI communications to initialize the device, setup resolution and color depth as well as refreshing the framebuffer data to the device memory on change.
 The resulting device created by the combination of this unit and a device specific driver is registered with Ultibo as a framebuffer device that can be accessed using all of the standard framebuffer API functions.