From eef7ae01a9757f5e4a0693d539ee1fac5b09e756 Mon Sep 17 00:00:00 2001
From: scuri
Microsoft Windows: can be the handle of the Windows window (HWND), +
GDI and GDI+: can be the handle of the Windows window (HWND),
or the handle of a previously created Device Context (HDC), or can be a string in the
format "hdc width height" or, in C, "%p %d %d".
To get the entire screen use a NULL data.
- X-Windows: It is a string in the format "display window" or, in C, "%p
- %lu" (uses the default screen).
The given parameters must exists until cdKillCanvas is called. The +
The given parameters must exists until cdKillCanvas is called. + In Windows, the HDC is released only if created inside cdCreateCanvas from an HWND or when data is NULL.
Any amount of such canvases may exist simultaneously, but they should not use the same window, except if you are using a GDI canvas and a GDI+ canvas at the same time for the same window.
-In CDLUA, the creation parameter must be a string in X-Windows and a userdata in Microsoft Windows.
-To use this driver in Windows using GDI+ is necessary to call - - cdUseContextPlus(1) -before creating the canvas.
+In CDLUA, the creation parameter must be a string in X-Windows and a userdata in + others.
This driver is greatly platform-dependent. For further detail, see the Behavior of Functions in each - platform: Microsoft Windows (GDI), Windows Using GDI+, - X-Windows (XLIB), GDK. However, it should be noted that some functions behave differently from the - basic functions of each platform.
+This driver is very platform-dependent.
+ +For further detail, see the + Behavior of Functions in each base driver: GDI, + GDK and X-Win. To use this driver + with a context plus base driver is necessary to call + + cdUseContextPlus(1) + before creating the canvas, see the GDI+, Cairo +and XRender base drivers.
+However, it should be noted that some functions behave differently from the +basic functions of each platform.