From 7b52cc13af4e85f1ca2deb6b6c77de9c95ea0dcf Mon Sep 17 00:00:00 2001 From: scuri Date: Fri, 17 Oct 2008 06:10:33 +0000 Subject: First commit - moving from LuaForge to SourceForge --- html/en/drv/cgm.html | 184 ++++++++++++++++++++++++++++++++++++++ html/en/drv/clipbd.html | 68 ++++++++++++++ html/en/drv/dbuf.html | 71 +++++++++++++++ html/en/drv/dbufrgb.html | 60 +++++++++++++ html/en/drv/debug.html | 64 +++++++++++++ html/en/drv/dgn.html | 161 +++++++++++++++++++++++++++++++++ html/en/drv/dxf.html | 180 +++++++++++++++++++++++++++++++++++++ html/en/drv/emf.html | 84 ++++++++++++++++++ html/en/drv/gdiplus.html | 200 +++++++++++++++++++++++++++++++++++++++++ html/en/drv/image.html | 57 ++++++++++++ html/en/drv/irgb.html | 117 ++++++++++++++++++++++++ html/en/drv/iup.html | 65 ++++++++++++++ html/en/drv/mf.html | 80 +++++++++++++++++ html/en/drv/native.html | 91 +++++++++++++++++++ html/en/drv/pdf.html | 227 +++++++++++++++++++++++++++++++++++++++++++++++ html/en/drv/picture.html | 81 +++++++++++++++++ html/en/drv/printer.html | 83 +++++++++++++++++ html/en/drv/ps.html | 208 +++++++++++++++++++++++++++++++++++++++++++ html/en/drv/sim.html | 90 +++++++++++++++++++ html/en/drv/win32.html | 137 ++++++++++++++++++++++++++++ html/en/drv/wmf.html | 116 ++++++++++++++++++++++++ html/en/drv/xrender.html | 152 +++++++++++++++++++++++++++++++ html/en/drv/xwin.html | 129 +++++++++++++++++++++++++++ 23 files changed, 2705 insertions(+) create mode 100644 html/en/drv/cgm.html create mode 100644 html/en/drv/clipbd.html create mode 100644 html/en/drv/dbuf.html create mode 100644 html/en/drv/dbufrgb.html create mode 100644 html/en/drv/debug.html create mode 100644 html/en/drv/dgn.html create mode 100644 html/en/drv/dxf.html create mode 100644 html/en/drv/emf.html create mode 100644 html/en/drv/gdiplus.html create mode 100644 html/en/drv/image.html create mode 100644 html/en/drv/irgb.html create mode 100644 html/en/drv/iup.html create mode 100644 html/en/drv/mf.html create mode 100644 html/en/drv/native.html create mode 100644 html/en/drv/pdf.html create mode 100644 html/en/drv/picture.html create mode 100644 html/en/drv/printer.html create mode 100644 html/en/drv/ps.html create mode 100644 html/en/drv/sim.html create mode 100644 html/en/drv/win32.html create mode 100644 html/en/drv/wmf.html create mode 100644 html/en/drv/xrender.html create mode 100644 html/en/drv/xwin.html (limited to 'html/en/drv') diff --git a/html/en/drv/cgm.html b/html/en/drv/cgm.html new file mode 100644 index 0000000..17ca141 --- /dev/null +++ b/html/en/drv/cgm.html @@ -0,0 +1,184 @@ + + + + + + +CD_CGM + + + + + +

CD_CGM - Computer Graphics Metafile Driver (cdcgm.h)

+ +

This driver allows generating a Computer Graphics Metafile, which is an ANSI standard for the persistent storage of + graphics primitives. The file usually has an extension .CGM.

+ +

Use

+ +

The file file is created by means of a call to the function + cdCreateCanvas(CD_CGM, + Data), which opens the file and writes its header. Then, other functions in the CD library can be called + as usual. The Data parameter string has the following format:

+ + 
"filename [widthxheight] [resolution] [-t] -p[precision]" or in C style "%s %gx%g %g %s"
+ +

Only the parameter filename is required. The filename must be inside double quotes (") + if it has spaces. Width and height are provided in millimeters + (note the lowercase "x" between them), and their default value in pixels is INT_MAX for + both dimensions. When the canvas' size is not specified, the VDC Extension saved to the file is the image's bounding + rectangle. The resolution is the number of pixels per millimeter; its default value is "3.78 pixels/mm" (96 DPI). + Width, height and resolution are + real values. Width, height and resolution + are used only by cdGetCanvasSize and in pixel-millimeter conversion. + Parameter -t modifies the codification. Parameter -p specifies + the precision of integers, which can be 16 (default) or 32.

+

Any amount of such canvases may exist simultaneously. It is important to note that a call to function + + cdKillCanvas is required to close the file properly.

+

Coding - The CGM format supports binary and text coding. If you are not sure what to do, use + binary coding, which is the default. Should you prefer text coding, add a "-t" string to + the Data parameter.

+

Precision of Coordinates - The primitives can use coordinates in real numbers. However, for + compatibility reasons, we use coordinates in integers.

+ +

Behavior of Functions

+

Control 

+ +

Coordinate System and Clipping

+ +

Primitives

+ +

Attributes

+ +
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Font Mapping
CD FontsGenerated Font Names
CD_PLAINCD_BOLDCD_ITALICCD_BOLD|CD_ITALIC
"System""SYSTEM""SYSTEM_BOLD""SYSTEM_ITALIC""SYSTEM_BOLDITALIC"
"Courier""COURIER" "COURIER_BOLD" "COURIER_ITALIC" "COURIER_BOLDITALIC"
"Times""TIMES_ROMAN" "TIMES_ROMAN_BOLD""TIMES_ROMAN_ITALIC""TIMES_ROMAN_BOLDITALIC"
"Helvetica""HELVETICA" "HELVETICA_BOLD""HELVETICA_ITALIC""HELVETICA_BOLDITALIC"
+
+
+

Colors

+ +

Client Images 

+ +

Server Images

+ + + + + diff --git a/html/en/drv/clipbd.html b/html/en/drv/clipbd.html new file mode 100644 index 0000000..0b9be2d --- /dev/null +++ b/html/en/drv/clipbd.html @@ -0,0 +1,68 @@ + + + + + + +CD_CLIPBOARD + + + + + +

CD_CLIPBOARD - Clipboard Driver (cdclipbd.h)

+ +

This driver allows the access to a Clipboard area. It is greatly dependent + on the system. In Win32, it creates an Enhanced Metafile, + a Bitmap or a CD Metafile; in X-Windows it + creates only a CD Metafile.

+ +

Use

+ +

The canvas is created by means of a call to function + + cdCreateCanvas(CD_CLIPBOARD, Data), after which + other functions in the CD library can be called as usual. The + Data parameter string is platform-dependent and + varies according to the metafile created. See each metafile's documentation, + but remember to exclude parameter "filename".

+

In the Windows environment, if the string "-b" + is present, it means that a Bitmap must be created instead of a + metafile, and, if the string "-m" is specified, a + CD Metafile will be created. For a Bitmap the remaining string + must contains the bitmap size and optionally its resolution: "-b + widthxheight [resolution]" or in C "%dx%d %g", + the resolution default is the screen resolution.

+

In the X-Windows environment, the Display ("%p") + where the data will be stored must be passed as a parameter before the CD + Metafile parameters. This environment's driver is used only for + applications that use CD to communicate with each other, because only CD Metafiles + are created.

+

Any amount of such canvases may exist simultaneously. It is important to + note that a call to function + + cdKillCanvas is required to + properly copy the data to the Clipboard.

+

You can interpret the data from the Clipboard using function cdPlay. In the X-Windows environment, the + parameter "data" for the cdPlay + function is the pointer to the + Display where the metafile will be obtained. The cdRegisterCallback + must be called for the driver that will interpret the file, except for bitmaps + that the CD_CLIPBOARD driver must be used.

+

To use this driver in Windows using GDI+ is necessary to call + + cdUseContextPlus(1) +before creating the canvas.

+ +

Behavior of Functions

+ +

This driver is greatly platform-dependent. For further detail, see the + Behavior of Functions in each platform: Microsoft + Windows (GDI), X-Windows (XLIB). However, it + should be noted that some functions behave differently from the basic + functions of each platform.

+ + + + + diff --git a/html/en/drv/dbuf.html b/html/en/drv/dbuf.html new file mode 100644 index 0000000..37b5c89 --- /dev/null +++ b/html/en/drv/dbuf.html @@ -0,0 +1,71 @@ + + + + + + +CD_DBUFFER + + + + + +

CD_DBUFFER - Double Buffer Driver using a server image (cddbuf.h)

+ +

Implements the concept of offscreen drawing. It is based on a Server Image + (the back buffer) and a Window canvas (the front buffer).

+ +

Use

+ +

The canvas is created by means of a call to function + + cdCreateCanvas(CD_DBUFFER, + Data), after which other functions in the CD library can be called as + usual. This function creates a CD canvas to use with an existing window canvas + (Native Windows or IUP). The parameter Data is a + pointer to the already created canvas.

+

Any amount of such canvases may exist simultaneously. It is important to + note that a call to function + + cdKillCanvas is required to + properly end the driver. Call function + + cdKillCanvas for this driver + before calling cdKillCanvas for + the window driver.

+

The drawing functions will work normally as if they were drawn on + the server image driver. When function + + cdCanvasFlush is executed, the image is drawn in the window canvas + passed as parameter in the canvas creation.

+

When the window's size changes, the server image is automatically recreated + using the same size as the canvas. This is done in the function + + + cdCanvasActivate.

+

We suggest you to implement rubber bands using XOR directly on the front +buffer.

+

To use this driver in Windows using GDI+ is necessary to call + + cdUseContextPlus(1) +before creating the canvas.

+ +

Behavior of Functions

+ +

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). However, it should be noted that + some functions behave differently from the basic functions of each platform.

+

Control

+ +

 

+ + + + + diff --git a/html/en/drv/dbufrgb.html b/html/en/drv/dbufrgb.html new file mode 100644 index 0000000..a9fa4c8 --- /dev/null +++ b/html/en/drv/dbufrgb.html @@ -0,0 +1,60 @@ + + + + + + +CD_DBUFFER + + + + + +

CD_DBUFFERRGB - Double Buffer Driver using a RGB image (cdirgb.h)

+ +

Implements the concept of offscreen drawing. It is based on a Image + RGB (the back buffer) and any other canvas (the front buffer).

+ +

Use

+ +

The canvas is created by means of a call to function + + cdCreateCanvas(CD_DBUFFERRGB, + Data), after which other functions in the CD library can be called as + usual. This function creates a CD canvas to use with any existing canvas. The parameter Data is a + pointer to the already created canvas.

+

Any amount of such canvases may exist simultaneously. It is important to + note that a call to function + + cdKillCanvas is required to + properly end the driver. Call function + + cdKillCanvas for this driver + before calling cdKillCanvas for + the client canvas driver.

+

The drawing functions will work normally as if they were drawn on + the image RGB driver. When function + + cdCanvasFlush is executed, the image is drawn in the canvas + passed as parameter in the canvas creation.

+

When the window's size changes, the RGB image is automatically recreated + using the same size as the canvas. This is done in the function + + + cdCanvasActivate.

+ +

Behavior of Functions

+ +

This driver depends on the RGB Client Image Driver.

+

Control

+ +

 

+ + + + + diff --git a/html/en/drv/debug.html b/html/en/drv/debug.html new file mode 100644 index 0000000..e405dac --- /dev/null +++ b/html/en/drv/debug.html @@ -0,0 +1,64 @@ + + + + + + +CD_METAFILE + + + + + +

CD_DEBUG - CD Debug Driver (cddebug.h)

+ +

This driver creates a text file with a log of all function calls. But for + only the functions that have a driver implementation and in the order that + the driver implements sequece of functions like Begin/Vertex/End. Pointers + are stored as addresses, and definitions are stored as the CD definition + "CD_XXX".

+ +

Use

+ +

The file is created by calling function + cdCreateCanvas(CD_DEBUG, + Data). The Data parameter is a string that must contain the filename and the canvas + dimensions, in the following format:

+ + 
"filename [widthxheight resolution]" or in C use "%s %gx%g %g"
+ +

Only the parameter filename is required. The filename must be inside double quotes (") + if it has spaces. Width and height are provided in millimeters + (note the lowercase "x" between them), and their default value in pixels is INT_MAX for + both dimensions. Resolution is the number of pixels per millimeter; its default value is + "3.78 pixels/mm" (96 DPI). Width, height and + resolution are real values.

+

Any amount of such canvases may exist simultaneously. It is important to note that a call to function + + cdKillCanvas is required to close the file properly.

+ +

Behavior of Functions

+

Coordinate System and Clipping

+ +

Attributes

+ +
  • FontDim: + uses a size estimator, returning approximate values.
    • +
  • + TextSize: uses a size estimator, returning approximate values.
    • +     +

    Colors

    + + + + + diff --git a/html/en/drv/dgn.html b/html/en/drv/dgn.html new file mode 100644 index 0000000..acd688b --- /dev/null +++ b/html/en/drv/dgn.html @@ -0,0 +1,161 @@ + + + + + + +CD_DGN + + + + + +

    CD_DGN - MicroStation Design File Driver (cddgn.h)

    + +

    This driver allows generating a MicroStation design file. The file name usually has an extension .DGN. The driver + supports only MicroStation version 4.0 or later. The format's copyrights are property of + Bentley Systems.

    + +

    Use

    + +

    The file is created and opened by calling function + cdCreateCanvas(CD_DGN, + Data), in which Data contains the filename and canvas dimensions. This function + opens the file and writes its header. Then, other functions in the CD library can be called as usual. The + Data parameter string has the following format:

    + + 
    "filename [widthxheight] [resolution] [-f] [-sseedfile]"   or in C "%s %gx%g %g %s"
    + +

    Only the parameter filename is required. The filename must be inside double quotes (") + if it has spaces. Width and height are provided in millimeters + (note the lowercase "x" between them), and their default value in pixels is INT_MAX for + both dimensions. Resolution is the number of pixels per millimeter; its default value is + "3.78 pixels/mm" (96 DPI). Width, height and + resolution are real values. Parameter -f modifies the polygon + filling's behavior. Just as in MicroStation, you can specify a seed file using parameter -s. + Width, height and resolution are + used only by + cdCanvasGetSize and in + pixel-millimeter conversion. 

    +

    Any amount of such canvases may exist simultaneously. It is important to note that a call to function + + cdKillCanvas is required to close the file properly.

    +

    Images and Colors - The DGN format does not support server images and works with an indexed-color format. + Color quality is limited to 256 colors, and the format uses a uniform palette to convert RGB colors into palette + indices. If you configure a palette, the color conversion process will become slower.

    +

    Filling - Up to version 5.0, MicroStation presents some limitations for polygon filling. You can disable + filling by means of string "-f" in the Data parameter. Filled + polygons can only have around 10,000 vertices; if the value is larger, the polygon style changes to closed lines.

    +

    Seed - In the seed file, several DGN parameters can be defined to be used in the drawing. The library offers + a default seed file, called "SEED2D.DGN". The file's location depends on the environment variable CDDIR.

    + +

    Behavior of Functions

    +

    Control

    + +

    Coordinate System and Clipping

    + +

    Primitives

    + +

    Attributes

    + +
    +
    + + + + + + + + + + + + + + + + + + + + + + +
    Font Mapping
    CD FontsMicroStation Font Index
    CD_SYSTEM0
    CD_COURIER 1
    CD_TIMES_ROMAN2
    CD_HELVETICA3
    +
    +
    +

    Colors

    + +

    Client Images

    + +

    Server Images

    + + + + + diff --git a/html/en/drv/dxf.html b/html/en/drv/dxf.html new file mode 100644 index 0000000..95274ee --- /dev/null +++ b/html/en/drv/dxf.html @@ -0,0 +1,180 @@ + + + + + + +CD_DXF + + + + + +

    CD_DXF - AutoCAD Image Exchange File Driver (cddxf.h)

    + +

    This driver allows generating an AutoCAD image exchange file. The file name usually has an extension .DXF. This + driver supports only AutoCAD version 10.0 or later. The format's copyrights are property of + Autodesk.

    + +

    Use

    + +

    The file is created and opened by calling function + cdCreateCanvas(CD_DXF, + Data), in which Data contains the file name and canvas dimensions. This function + opens the file and writes its header. Then, other functions in the CD library can be called as usual. The + Data parameter string has the following format:

    + + 
    "filename [widthxheight] [resolution]"    or in C "%s %gx%g %g"
    + +

    Only the parameter filename is required. The filename must be inside double quotes (") + if it has spaces. Width and height are provided in millimeters + (note the lowercase "x" between them), and their default value in pixels is INT_MAX for + both dimensions. Resolution is the number of pixels per millimeter; its default value is + "3.78 pixels/mm" (96 DPI). Width, height and + resolution are given in real values and are used only by + + cdCanvasGetSize and in pixel-millimeter conversion. 

    +

    Any amount of such canvases may exist simultaneously. It is important to note that a call to function + + cdKillCanvas is required to close the DXF file properly.

    +

    Images - The DXF format does not support client or server images and works with an indexed-color format + (color quality is limited to 256 fixed colors).

    +

    Precision of Coordinates - The primitives use coordinates in real numbers.

    +

    Layers - The format can work with several layers. It is necessary to draw the primitives of layer + '0' first, then layer '1' and so on. Use functions + Flush + to change the current layer.

    + +

    Behavior of Functions

    +

    Control

    + +

    Coordinate System and Clipping

    + +

    Primitives

    + +

    Attributes

    + +
    +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Font Mapping
    CD FontsAutoCAD Fonts
    SystemSTANDARD (sem arquivo)
    CourierROMAN (romanc.shx)
    Courier + CD_BOLDROMAN_BOLD (romant.shx)
    TimesROMANTIC (rom_____.pfb)
    Times + CD_BOLDROMANTIC_BOLD (romb_____.pfb)
    HelveticaSANSSERIF (sas_____.pfb)
    Helvetica + CD_BOLDSANSSERIF_BOLD (sasb____.pfb)
    +
    +
    +

    Colors

    + +

    Client Images

    + +

    Server Images

    + +

     

    + + + + diff --git a/html/en/drv/emf.html b/html/en/drv/emf.html new file mode 100644 index 0000000..1f7b462 --- /dev/null +++ b/html/en/drv/emf.html @@ -0,0 +1,84 @@ + + + + + + +CD_EMF + + + + + +

    CD_EMF - Enhanced Metafile Driver (cdemf.h)

    + +

    This driver allows generating a Microsoft Windows Enhanced Metafile, the + format used by 32-bit Windows systems to store graphics primitives. Usually, + the filename has an extension "*.emf".

    +

    The driver works only in the Microsoft Windows platform, but you can use it + in other platforms without the risk of compilation error. If you attempt to + create a canvas in another platform, function + cdCreateCanvas will return NULL.

    + +

    Use

    + +

    The canvas is created by means of a call to function + + cdCreateCanvas(CD_EMF, Data), after which other CD + functions can be called as usual. Parameter Data + has the following format:

    + + 
    "filename widthxheight"     or in C "%s %dx%d"
    + +

    It must include the filename and the canvas' dimensions. + The filename must be inside double quotes (") if it has spaces. + Width and height are provided in pixels + (note the lowercase "x" between them). Resolution (the number of pixels per + millimeter) is always the screen resolution.

    +

    Any amount of such canvases may exist simultaneously. Function + cdCreateCanvas opens the + file, and a call to function + + cdKillCanvas is required to + close the file properly.

    +

    To use this driver in Windows using GDI+ is necessary to call + + cdUseContextPlus(1) +before creating the canvas. If you intend to use cdCanvasPlay +to interpret the EMF, then do not use GDI+ to generate the metafile. GDI+ +extensively use internal transformations that will affect the +cdCanvasPlay interpretation. Also some interior style will not be +correctly interpreted.

    + +

    Behavior of Functions

    + +

    This driver is greatly platform-dependent. For further detail, see the + Behavior of Functions of the Microsoft Windows (GDI) + or Windows Using GDI+ platform base drivers. It has + been noticed that EMF, when saved in the Windows 95 environment, is not + totally compatible with EMF saved in the Windows NT environment.

    + +

    Control Functions

    + +

    Client Images 

    + +

    Server Images

    + + + + + diff --git a/html/en/drv/gdiplus.html b/html/en/drv/gdiplus.html new file mode 100644 index 0000000..e4a2810 --- /dev/null +++ b/html/en/drv/gdiplus.html @@ -0,0 +1,200 @@ + + + + + +GDI+ + + + + + +

    Microsoft Windows Base Driver Using GDI+

    + +

    This driver represents a base driver for all system-dependent drivers implemented in the Microsoft Windows system, + but uses a new API called GDI+. The drivers Clipboard, Native Window, IUP, Image, Printer, + EMF and Double Buffer were implemented. The driver WMF, and the function + cdPlay of the Clipboard and EMF drivers were not implemented using GDI+.

    +

    The main motivation for the use of GDI+ was transparency for all the primitives. Beyond that we got other features + like anti-aliasing, gradient filling, bezier lines and filled cardinal splines.

    +

    This driver still does not completely replace the GDI Windows base driver, because GDI+ does not have support for + XOR. Also the applications need to adapt the rendering of text that is slightly different from GDI. It is know that + GDI+ can be slower than GDI in some cases and faster in other cases, Microsoft does not make this clear.

    +

    So we let the programmer to choose what to use. We created the function + cdUseContextPlus that allows to activate or to deactivate the use of GDI+ for the available + Windows based drivers. + This function affects only the cdCreateCanvas function call, once created + the canvas will be always a GDI+ canvas. In fact the function affects primary the definitions + CD_NATIVEWINDOW, + CD_IMAGE, + CD_PRINTER, + CD_EMF, + CD_DBUFFER and + CD_CLIPBOARD, because they are + function calls and not static defines.

    +

    Using GDI+ it is allowed to create more that one canvas at the same time for the same Window. And they can co-exist + with a standard GDI canvas.

    +

    To enable the use of GDI+ based drivers you must call the initialization function + cdInitContextPlus() once and link to the libraries "cdcontextplus.lib" and "gdiplus.lib". + Also the file "gdiplus.dll" must be available in your system. These files already came with Visual + C++ 7 and Windows XP. For other compilers or systems you will need to copy the ".lib" file for you libraries area, and + you will need to copy the DLL for the Windows\System (Win98/Me) or Windows\System32 (Win2000/NT4-SP6) folder. The + gdiplus files can be obtained from + + Microsoft or from here.

    +

    In CDLua it is not necessary any additional initialization, but the + application must still be linked with the cdcontextplus.lib + library or a require"cdluacontextplus" can be used when + using dynamic libraries.

    + +

    Behavior of Functions

    +

    Control

    + +

    Coordinate System and Clipping

    + +

    Primitives

    + +

    Attributes

    + +

    Colors

    + +

    Client Images

    + +

    Server Images

    + +

    Exclusive Attributes

    + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/html/en/drv/image.html b/html/en/drv/image.html new file mode 100644 index 0000000..f19b3b3 --- /dev/null +++ b/html/en/drv/image.html @@ -0,0 +1,57 @@ + + + + + + +CD_IMAGE + + + + + +

    CD_IMAGE - Server Image Driver (cdimage.h)

    + +

    This driver provides access to a Server Image, a memory-based + high-performance image that corresponds to the attributes of the system's + devices. It is used for offscreen drawings.

    + +

    Use

    + +

    The canvas is created by means of a call to function + + cdCreateCanvas(CD_IMAGE, + Data), after which other functions in the CD library can be called as + usual. The function creates a CD canvas based on an existing Server Image. The + Data parameter must be a pointer to an image + created with function  + + cdCreateImage.

    +

    Any amount of such canvases may exist simultaneously. It is important to + note that a call to function + + cdKillCanvas is required to + properly end the driver. You can call function + + cdKillImage only after + calling cdKillCanvas.

    +

    For use with CDLUA, the Server Image passed as parameter must have been + created with function cd.CreateImage + in Lua.

    +

    To use this driver in Windows using GDI+ is necessary to call + + cdUseContextPlus(1) +before creating the canvas.

    + +

    Behavior of Functions

    + +

    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). However, it should be noted that + some functions behave differently from the basic functions of each platform.

    + + + + + diff --git a/html/en/drv/irgb.html b/html/en/drv/irgb.html new file mode 100644 index 0000000..3ab71f4 --- /dev/null +++ b/html/en/drv/irgb.html @@ -0,0 +1,117 @@ + + + + + + +CD_IMAGERGB + + + + + +

    CD_IMAGERGB - RGB Client Image Driver (cdirgb.h)

    + +

    This driver allows access to a Client Image, an imaged based in RGB colors with 24 + or 32 bits per pixel (8 per channel). + It is used to implement high-quality offscreen drawings, but is slower than the Server Image version. In fact, it is a + rasterizer, that is, it converts vector primitives into a raster representation. All primitives are implemented by the + library and are not system-dependent (the primitives of the Server Image version are system-dependent).

    + +

    Use

    + +

    The canvas is created by means of a call to the function + cdCreateCanvas(CD_IMAGERGB, + Data), after which other functions in the CD library can be called as usual. The function creates an RGB image, + and then a CD canvas. The Data parameter string has the following format:

    + + 
    "widthxheight [r g b] -r[resolution]"      in C "%dx%d %p %p %p -r%g"
+or
+"widthxheight [r g b a] -r[resolution] -a"    in C "%dx%d %p %p %p %p -r%g -a"
    + +

    It must include the canvas' dimensions. Width and height + are provided in pixels (note the lowercase "x" between them). As an option, you can specify the buffers to be used by + the driver, so that you can draw over an existing image. The resolution can be defined with parameter + -r; its default value is "3.78 pixels/mm" (96 DPI). 

    +

    When the parameter -a is specified an alpha channel will be added to the +canvas underlying image. All primitives will be composed using an over operator +if the foreground or background colors have alpha components. This channel is +initialized with transparent (0). The other channels are initialized with white +(255, 255, 255). After drawing in the RGBA image the resulting alpha channel can +be used to compose the image in another canvas.

    +

    All channels are initialized only when allocated internally by the driver. +They are not initialized when allocated by the application.

    +

    Any amount of such canvases may exist simultaneously. It is important to note that a call to function + cdKillCanvas is required to + release internal allocated memory.

    +

    In Lua, the canvas can be created in two ways: with an already defined image or without it. With an image, an RGB + image must be passed as parameter, created by functions + cd.CreateImageRGB, + cd.CreateImageRGBA or + cd.CreateBitmap + in Lua. The resolution must be passed in an extra parameter after the image.

    + +

    Exclusive Functions

    + +

    cd.ImageRGB(canvas: cdCanvas) -> (imagergb: cdImageRGB +or cdImageRGBA) [in Lua]
    +cd.ImageRGBBitmap(canvas: cdCanvas) -> (bitmap: cdBitmap) [in Lua]

    + +

    Returns the canvas' internal image.

    + +

    Behavior of Functions

    + +

    All primitives are from the Simulation driver, see the Simulation driver's documentation for + further information.

    + +

    Control

    + +

    Coordinate System and Clipping

    + +

    Colors

    + +

    Exclusive Attributes

    + + + + + + + + + \ No newline at end of file diff --git a/html/en/drv/iup.html b/html/en/drv/iup.html new file mode 100644 index 0000000..90f11d9 --- /dev/null +++ b/html/en/drv/iup.html @@ -0,0 +1,65 @@ + + + + + + +CD_IUP + + + + + +

    CD_IUP - IUP Driver (cdiup.h)

    + +

    This driver provides access to an interface element of a IUP canvas. IUP is a portable user-interface library used + to create portable user-interface applications. See + IUP documentation.

    + +

    Use

    + +

    The canvas is created by means of a call to the function + cdCreateCanvas(CD_IUP, + Data), after which other CD functions can be called as usual. This function creates a CD canvas based on the + existing IUP canvas. The parameter Data is a pointer to a handle of the IUP canvas (Ihandle*). + For use with CDLUA, a canvas created with IUPLUA must necessarily be passed as parameter.

    +

    Any amount of such canvases may exist simultaneously, but they should not use the same IUP canvas. It is important + to note that a call to function + cdKillCanvas is required to close the file properly.

    +

    The CD canvas is automatically stored in the IUP canvas as the "_CD_CANVAS" + attribute.

    + + + +

    To use this driver, it must be linked with the "iupcd" + library available in the + IUP distribution.

    +

    In Lua, it is necessary to call function cdluaiup_open() after a call + to function cdlua_open(), apart from linking with the "iupluacd" + library. To use with require must be require"iupluacd" or require"iupluacd51".

    +

    To use this driver in Windows using GDI+ is necessary to call + + cdUseContextPlus(1) + before creating the canvas.

    + +

    Behavior of Functions

    + +

    This driver is greatly platform-dependent, but little dependent on the IUP library. For further detail, see the + Behavior of Functions in each platform: Microsoft Windows (GDI), + Windows Using GDI+, X-Windows (XLIB). However, it should be noted that some functions + behave differently from the basic functions of each platform.

    + +

    Control 

    + +

    Exclusive Attributes

    + + + + + diff --git a/html/en/drv/mf.html b/html/en/drv/mf.html new file mode 100644 index 0000000..c6157b9 --- /dev/null +++ b/html/en/drv/mf.html @@ -0,0 +1,80 @@ + + + + + + +CD_METAFILE + + + + + +

    CD_METAFILE - CD Metafile Driver (cdmf.h)

    + +

    This driver allows the generation of a CD Metafile, a very simple format that includes calls to functions of the CD + library and provides persistence to its primitives.

    + +

    Use

    + +

    The file is created by calling function + cdCreateCanvas(CD_METAFILE, + Data). The Data parameter is a string that must contain the filename and the canvas + dimensions, in the following format:

    + + 
    "filename [widthxheight resolution]" or in C use "%s %gx%g %g"
    + +

    Only the parameter filename is required. The filename must be inside double quotes (") + if it has spaces. Width and height are provided in millimeters + (note the lowercase "x" between them), and their default value in pixels is INT_MAX for + both dimensions. Resolution is the number of pixels per millimeter; its default value is + "3.78 pixels/mm" (96 DPI). Width, height and + resolution are real values.

    +

    Any amount of such canvases may exist simultaneously. It is important to note that a call to function + + cdKillCanvas is required to close the file properly.

    +

    Images - Be careful when saving images in the file, because it uses a text format to store all numbers and + texts of primitives, including images, which significantly increases its size.

    +

    Extension - Although this is not required, we recommend the extension used for the file to be ".MF".

    + +

    Behavior of Functions

    +

    Coordinate System and Clipping

    + +

    Attributes

    + +
  • FontDim: + uses a size estimator, returning approximate values.
    • +
  • + TextSize: uses a size estimator, returning approximate values.
    • +     +

    Colors

    + +

    Primitives

    + +

    Client Images

    + +

    Server Images

    + + + + + diff --git a/html/en/drv/native.html b/html/en/drv/native.html new file mode 100644 index 0000000..20d182a --- /dev/null +++ b/html/en/drv/native.html @@ -0,0 +1,91 @@ + + + + + + +CD_NATIVEWINDOW + + + + + +

    CD_NATIVEWINDOW - Native Window Driver (cdnative.h)

    + +

    This driver provides access to an existing Native Window, a basic element of the user-interface system. It also + provides access to other native handles like HDC handles in Windows.

    + +

    Use

    + +

    The canvas is created by means of a call to the function + cdCreateCanvas(CD_NATIVEWINDOW, + Data), after which other functions in the CD library can be called as usual. This function creates a CD + canvas based on an existing system canvas. The parameter Data is a pointer to a handle of + the canvas. It is system-dependent, having a different meaning in each platform:

    + +

    Microsoft Windows: 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 + 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.

    + +

    Exclusive Functions

    +

    void cdGetScreenSize(int *width, int *height, double *width_mm, double *height_mm); [in C]
    +cd.Get    ScreenSize() +-> (width, heigth, mm_width, mm_height: number) [in Lua]

    + +

    Equivalent to function + cdCanvasGetSize, but returns the values relative to the main screen of the + window system. It is not necessary to have an active canvas to call this function.

    + +

    int cdGetScreenColorPlanes(void); [in C]
    +cd.GetScreenColorPlanes() -> (bpp: number) [in Lua]

    + +

    Equivalent to function + cdCanvasGetColorPlanes, but returns the value relative to the main screen of the + window system. It is not necessary to have an active canvas to call this function.

    + +

    Behavior of Functions

    + +

    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). However, it should be noted that some functions behave differently from the + basic functions of each platform.

    + +

    Control

    + +

    Exclusive Attributes

    + + + + + diff --git a/html/en/drv/pdf.html b/html/en/drv/pdf.html new file mode 100644 index 0000000..71ee6b7 --- /dev/null +++ b/html/en/drv/pdf.html @@ -0,0 +1,227 @@ + + + + + + +CD_PDF + + + + + +

    CD_PDF - PDF Driver (cdpdf.h)

    + +

    This drivers allows generating a PDF file. This format developed for representing documents in a manner that is + independent of the original application software, hardware, and operating system used to create those documents. The + format's copyrights are property of Adobe Systems.

    +

    This driver is very similar to the PS driver but it uses the PDFlib library to generate the PDF (http://www.pdflib.com/). + There are two PDFlib licenses available, one commercial and one free with a flexible license, see + PDFlib Lite License. The CD_PDF driver works with both + versions.

    +

    By default the pre-compiled library in the distribution uses the PDF Lite version code. The configuration of the PDF Lite code +included does not supports image + file formats. The current PDF Lite version is 7.0.2.

    +

    PDFlib Copyright (c) 1997-2007 Thomas Merz and PDFlib GmbH. All rights reserved. Applications that use this driver + are subject to the PDFlib GmbH License Agreement.

    + +

    Use

    + +

    The file is created and opened by calling function + cdCreateCanvas(CD_PDF, + Data), in which Data contains the filename and canvas dimensions. This function + opens the file and writes its header. Then, other functions in the CD library can be called as usual. The + Data parameter string has the following format:

    + + 
    "filename -p[paper] -w[width] -h[height] -s[resolution] [-o]"
+or in C
+"%s -p%d -w%g -h%g -s%d -o"
    + +

    The filename must be inside double quotes (") if it has spaces. Any amount of such canvases may exist + simultaneously. It is important to note that a call to function + + cdKillCanvas is required to close the file properly.

    + + + +

    To use this driver, the application must be linked with the "cdpdf" + and "pdflib" libraries.

    +

    Paper Size - The default paper size is A4. It is possible to change it by using one of the predefined sizes + - CD_A0, CD_A1, CD_A2, CD_A3, + CD_A4, CD_A5, CD_LETTER and + CD_LEGAL - with parameter "-p". It is also possible to define a paper in a + particular size by using parameters "-w" e "-h". Values are + provided in millimeters.

    + +
    +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Default Paper Sizes
     Width (mm)Length (mm)
    A08411187
    A1594841
    A2420594
    A3297420
    A4210297
    A5148210
    Letter216279
    Legal216356
    +
    +
    + +

    Resolution - Resolution is used to convert values from millimeters to pixels (the same as points, but the + number of points is per inch - DPI). Use parameter "-s" to configure the resolution. The + default value is 300 DPI.

    +

    Orientation - The page can be oriented as portrait or landscape. The default value is portrait, but when the + parameter "-o" is used, the horizontal and vertical values are switched.

    +

    In Lua, it is necessary to call function cdluapdf_open() after a call + to function cdlua_open(), apart from linkediting with the "cdluapdf" + library.

    + +

    Behavior of Functions

    +

    Control

    + +

    Coordinate System & Clipping

    + +

    Attributes

    + +
    Courier, Courier-Bold, Courier-Oblique, Courier-BoldOblique,
+Helvetica, Helvetica-Bold, Helvetica-Oblique, Helvetica-BoldOblique,
+Times-Roman, Times-Bold, Times-Italic, Times-BoldItalic,
+Symbol, 
+ZapfDingbats
    +

    Colors

    + +

    Client Images

    + +

    Primitives

    + +

    Server Images

    + +

    Exclusive Attributes

    + + + + + + + + + + diff --git a/html/en/drv/picture.html b/html/en/drv/picture.html new file mode 100644 index 0000000..d702555 --- /dev/null +++ b/html/en/drv/picture.html @@ -0,0 +1,81 @@ + + + + + + +CD_METAFILE + + + + + +

    CD_PICTURE - CD Picture (cdpicture.h)

    + +

    This driver allows the creation of a CD Picture. It store primitives and + attributes in memory that can be played and resized in any other driver. It + does not includes clipping and WriteMode.

    + +

    Use

    + +

    The file is created by calling function + cdCreateCanvas(CD_PICTURE, + Data). The Data parameter is a string that + can contain the resolution in the following format:

    + + 
    "[resolution]" or in C use "%lg"
    + +

    Resolution is the number of pixels per millimeter; its default value is + "3.78 pixels/mm" (96 DPI).

    +

    The canvas size is automatically calculated to be the bounding box of all the +primitives inside the picture.

    +

    Any amount of such canvases may exist simultaneously. It is important to note that a call to function + + cdKillCanvas is required to release the picture memory.

    + +

    Behavior of Functions

    +

    Coordinate System and Clipping

    + +

    Attributes

    + +
  • + + WriteMode: does nothing.
    • +
  • FontDim: + uses a size estimator, returning approximate values.
    • +
  • + TextSize: uses a size estimator, returning approximate values.
    • +     +

    Colors

    + +

    Primitives

    + +

    Client Images

    + +

    Server Images

    + + + + + diff --git a/html/en/drv/printer.html b/html/en/drv/printer.html new file mode 100644 index 0000000..d354fe2 --- /dev/null +++ b/html/en/drv/printer.html @@ -0,0 +1,83 @@ + + + + + + +CD_PRINTER + + + + + +

    CD_PRINTER - Printer Driver (cdprint.h)

    + +

    This driver provides access to a System Default Printer.

    +

    Currently, it works only in Microsoft Windows platforms, but it is possible + to use it in other platforms without the risk of compilation error. If you + attempt to create a canvas in another platform, the function + + cdCreateCanvas will return + NULL.

    + +

    Use

    + +

    The canvas is created by calling function + + cdCreateCanvas(CD_PRINTER, Data), after which + other CD functions can be called as usual. The Data + string has the following format:

    + + 
    "name [-d]"    or in C style "%s -d"
    + +

    name is an optional document name that will + appear in the printer queue. Optionally, -d + displays the System Printer dialogue box before starting to print, allowing + you to configure the printer's parameters. When using this parameter and the + return canvas is NULL, one must assume that the print was canceled by the + user.

    +

    Any amount of such canvases may exist simultaneously. It is important to + note that a call to function + + cdKillCanvas is required to + properly send the data to the printer.

    +

    Pages - Use + + Flush to change to a new + page. You can draw first on page 1, then on page 2 and so forth.

    +

    To use this driver in Windows using GDI+ is necessary to call + + cdUseContextPlus(1) +before creating the canvas.

    + +

    Behavior of Functions

    + +

    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). However, it should be noted that + some functions behave differently from the basic functions of each platform.

    +

    A printer created in Win32s has the same limitations as the + WMF driver. In Windows 95 or NT, it has the same + limitations as the EMF driver.

    + +

    Control

    + +

    Attributes

    + + + + + diff --git a/html/en/drv/ps.html b/html/en/drv/ps.html new file mode 100644 index 0000000..7a2dc1a --- /dev/null +++ b/html/en/drv/ps.html @@ -0,0 +1,208 @@ + + + + + + +CD_PS + + + + + +

    CD_PS - PostScript Driver (cdps.h)

    + +

    This drivers allows generating a PostScript file. This format was created to be a high-quality graphics language + for printers and is currently supported by several printers. If your printer supports PostScript, you can send the + file generated by the driver directly to the printer port. Usually, the filename has an extension .PS or .EPS. The + driver generates level-2 PostScript, therefore some PostScript viewers might present errors. The format's copyrights + are property of Adobe Systems.

    + +

    Use

    + +

    The file is created and opened by calling function + cdCreateCanvas(CD_PS, + Data), in which Data contains the filename and canvas dimensions. This function + opens the file and writes its header. Then, other functions in the CD library can be called as usual. The + Data parameter string has the following format:

    + + 
    "filename -p[paper] -w[width] -h[height] -l[left] -r[right] -b[bottom] -t[top] -s[resolution] [-e] [-g] [-o] [-1] d[margin]"
    
+    or in C
    
+"%s -p%d -w%g -h%g -l%g -r%g -b%g -t%g -s%d -e -o -1 -g -d%g"
    + +

    The filename must be inside double quotes (") if it has spaces. Any amount of such canvases may exist + simultaneously. It is important to note that a call to function + + cdKillCanvas is required to close the file properly.

    +

    Paper Size - The default paper size is A4. It is possible to change it by using one of the predefined sizes + - CD_A0, CD_A1, CD_A2, CD_A3, + CD_A4, CD_A5, CD_LETTER and + CD_LEGAL - with parameter "-p". It is also possible to define a paper in a + particular size by using parameters "-w" e "-h". Values are + provided in millimeters.

    + +
    +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Default Paper Sizes
     Width (mm)Length (mm)
    A08411187
    A1594841
    A2420594
    A3297420
    A4210297
    A5148210
    Letter216279
    Legal216356
    +
    +
    + +

    Margins - The margins are controlled by parameters "-l" "-r" + "-t" and "-b" (left, right, top, bottom). Values are + provided in millimeters. Default margins are 25.4 mm to all parameters. You can draw only inside the margins.

    +

    Resolution - Resolution is used to convert values from millimeters to pixels (the same as points, but the + number of points is per inch - DPI). Use parameter "-s" to configure the resolution. The + default value is 300 DPI.

    +

    Orientation - The page can be oriented as portrait or landscape. The default value is portrait, but when the + parameter "-o" is used, the horizontal and vertical values are switched.

    +

    EPS - The PostScript file can be in an Encapsulated PostScript format. For such, + simply specify the parameter "-e". It is useful for other applications to import the + PostScript file. You can define the margins of the bounding box by means of parameter "-d", + in millimeters.

    +

    Debug - Parameter "-g" adds a series of comments to the PS file, making the + beginning and end of a command from the CD library explicit. It is useful only for those who understand PostScript and + wish to identify a problem. It considerably increases the file size.

    +

    Level 1 - Parameter "-1" forces the driver to generate a level-1 PostScript. In + this case, pattern, stipple and hatch are not supported.

    +

    Pages - Use function cdFlush to change to a new page. The previous page will not + be changed.

    + +

    Behavior of Functions

    +

    Control

    + +

    Coordinate System & Clipping

    + +

    Attributes

    + +

    Colors

    + +

    Client Images

    + +

    Primitives

    + +

    Server Images

    + +

    Exclusive Attributes

    + + + + + + + diff --git a/html/en/drv/sim.html b/html/en/drv/sim.html new file mode 100644 index 0000000..85a4e7f --- /dev/null +++ b/html/en/drv/sim.html @@ -0,0 +1,90 @@ + + + + +Simulation + + + + + +

    Simulation Base Driver

    + +

    The Simulation driver was created to simulate functions that were not supported by some CD drivers. It works + jointly with the other driver (known as "client"), using its pixel, line and text functions to simulate arcs, sectors, + polygons, boxes, and fillings with styles.

    +

    Important: All simulation primitives are based in the client's Pixel, Image and/or Line functions.

    + +

    Use

    + +

    The Simulation driver is used in several parts of the CD library.

    +

    In many drivers, the behavior of a given primitive may not be the expected. Usually this is documented in the + manual. If you wish to activate the simulation of a primitive, simply call function + cdSimulate + with the code of the primitive to be simulated.

    + +

    Behavior of Functions

    +

    Clipping

    + +

    Attributes

    + +

    Primitives

    + + +

    Exclusive Attributes

    + + + + + diff --git a/html/en/drv/win32.html b/html/en/drv/win32.html new file mode 100644 index 0000000..53ac2a5 --- /dev/null +++ b/html/en/drv/win32.html @@ -0,0 +1,137 @@ + + + + + + +Windows + + + + + +

    Microsoft Windows Base Driver

    + +

    This driver represents a base driver for all system-dependent drivers implemented in the Microsoft Windows system. + The implementation uses Win32 API graphics functions, the GDI. The driver works better in Windows NT, but it may also + work in Windows 9x/Me.

    + +

    Behavior of Functions

    +

    Control 

    + +

    Coordinate System and Clipping

    + +

    Primitives

    + +

    Attributes

    + +

    Client Images

    + +

    Colors

    + +

    Exclusive Attributes

    + + + + + + + + + + + \ No newline at end of file diff --git a/html/en/drv/wmf.html b/html/en/drv/wmf.html new file mode 100644 index 0000000..aa92c68 --- /dev/null +++ b/html/en/drv/wmf.html @@ -0,0 +1,116 @@ + + + + + + +CD_WMF + + + + + +

    CD_WMF - Windows Metafile Driver (cdwmf.h)

    + +

    This driver allows creating a Microsoft Windows Metafile, the format used + by 16-bit Windows systems to store graphics primitives. Usually, the filename + has an extension "*.wmf".

    +

    The driver works only in the Microsoft Windows platform, but you can use it + in other platforms without the risk of compilation error. If you attempt to + create a canvas in another platform, function + cdCreateCanvas will return NULL.

    +

    It is recomended to use EMF instead of WMF whenever is possible.

    + +

    Use

    + +

    The canvas is created by means of a call to the function + + + cdCreateCanvas(CD_WMF, Data), after which other + functions in the CD library can be called as usual. The + Data parameter string has the following format:

    + + 
    "filename widthxheight [resolution]"     or in C "%s 
+    %dx%d %g"
    + +

    The file's name and dimensions are required. Width + and height are provided in pixels (note the + lowercase "x" between them). Resolution is the + number of pixels per millimeter; its default value is the screen resolution.

    +

    Any amount of such canvases may exist simultaneously. Function + cdCreateCanvas creates a + memory-based metafile, and a call to function + + cdKillCanvas is required to + close the file properly.

    +

    In fact the driver uses a slightly different format, called Aldus Placeable + Metafile (APM). It attaches a small header to the beginning of the file, + allowing other applications to import better the metafile contents.

    +

    This + driver is NOT available for the GDI+ base driver.

    + +

    Behavior of Functions

    + +

    This driver is greatly platform-dependent. For further detail, see the + Behavior of Functions of the Microsoft Windows + (GDI) platform. However, it should be noted that some functions behave + differently from the basic functions of each platform.

    + +

    Control 

    + +

    Coordinate System and Clipping

    + +

    Attributes

    + +

    Client Images 

    + +

    Server Images

    + + + + + diff --git a/html/en/drv/xrender.html b/html/en/drv/xrender.html new file mode 100644 index 0000000..6970e29 --- /dev/null +++ b/html/en/drv/xrender.html @@ -0,0 +1,152 @@ + + + + + + +X-Windows + + + + + +

    XRender Base Driver

    + +

    This driver represents a basic driver for all system-dependent drivers + implemented in the X-Windows system using the XRender extension. The implementation uses the + XRender and Xft API functions.

    +

    The main motivation for the use of XRender was transparency for all the primitives. Beyond that we got other features + like anti-aliasing, gradient filling and transformations.

    +

    This driver still does not completely replace the X-Windows base driver, because + XRender does not have support for + XOR and for line styles.

    +

    So we let the programmer to choose what to use. We created the function + cdUseContextPlus that allows to activate or to deactivate the use of + X-Render for the available X-Windows based drivers. + This function affects only the cdCreateCanvas function call, once created + the canvas will be always a XRender canvas. In fact the function affects primary the definitions + CD_NATIVEWINDOW, + CD_IMAGE and + CD_DBUFFER, because they are + function calls and not static defines.

    +

    Using XRender it is allowed to create more that one canvas at the same time for the same Window. And they can co-exist + with a standard X-Windows canvas.

    +

    To enable the use of XRender based drivers you must call the initialization function + cdInitContextPlus() once and link to the libraries "cdcontextplus", "Xrender" and "Xft". + Also the libraries "Xrender" and "Xft" + must be installed in your system. The XRender extension must be available in + the X-Windows server for the driver to work.

    +

    Currently, pre-compiled binaries are available for Linux, Darwin +and FreeBSD54. It is not available for the systems we have with AIX, SunOS and +IRIX.

    +

    In CDLua it is not necessary any additional initialization, but the + application must still be linked with the cdcontextplus.lib + library or a require"cdluacontextplus" can be used when + using dynamic libraries.

    + +

    Behavior of Functions

    +

    Control 

    + +

    Coordinate System and Clipping

    + +

    Primitives

    + +

    Attributes

    + +

    Colors

    + +

    Client and Server Images

    + +

    Exclusive Attributes

    + + + + + + + + + + + + + diff --git a/html/en/drv/xwin.html b/html/en/drv/xwin.html new file mode 100644 index 0000000..cd2d900 --- /dev/null +++ b/html/en/drv/xwin.html @@ -0,0 +1,129 @@ + + + + + + +X-Windows + + + + + + +

    X-Windows Base Driver

    + +

    This driver represents a basic driver for all system-dependent drivers + implemented in the X-Windows system. The implementation uses the XLIB API + functions. It was developed using X11R4, but works in more recent versions, + such as X11R6.

    +

    Note: The coordinates internally implemented by the video driver use 16-bit + integers. Therefore, if a coordinate with less than -32k or more than 32k is + defined, it will be interpreted incorrectly.

    + +

    Behavior of Functions

    +

    Control 

    + +

    Coordinate System and Clipping

    + +

    Primitives

    + +

    Attributes

    + +

    Colors

    + +

    Client Images

    + +

    Exclusive Attributes

    + + + + + + + -- cgit v1.2.3