This back-end behaves like TGDIBackend in what features it supports. However it is different from TGDIBackend in the way the memory for the surface is allocated: Instead of allocating in RAM the memory backing the surface is allocated in so called memory-mapped files. A memory-mapped file is a segment of virtual memory which has been assigned a direct byte-for-byte correlation with some portion of a (temporary) file or swap file for that matter.
This approach may allow allocating large bitmaps that would otherwise not be allocateable by the GDI subsystem. The drawback is reduced performance due to swapping to and from disk that may occur.
| Methods | Properties | Events |
|---|---|---|
| In TGDIMMFBackend: | ||
| Create | ||
| In TBackend: | ||
| Assign | Bits | OnChanging |
| ChangeSize | ||
| Changing | ||
| Clear | ||
| Destroy | ||
| Empty | ||
| FinalizeSurface | ||
| InitializeSurface | ||
| In TThreadPersistent: | ||
| Lock | LockCount | |
| Unlock | ||
| In TNotifiablePersistent: | ||
| BeginUpdate | UpdateCount | OnChange |
| Changed | ||
| EndUpdate | ||
Copyright ©2000-2024 Alex Denisov and the Graphics32 Team - Graphics32 2.0 - Help file built on 18 Feb 2024