TBarCode Library 11
TBarCode Library 11
|
typedef ERRCODE | ( | TEC_CALLBACK * | fn_DrawHexagon | ) |
Callback-function which is called instead of drawing a barcode row.
Data type for custom MaxiCode hexagon drawing callback-function.
Data type for custom MaxiCode finder drawing callback-function.
Data type for custom human readable text drawing callback-function.
XXX.
Data type for custom bar-drawing callback-function.
This callback function can be set with BCSetFuncDrawRow(). When set the drawing functions such as BCDraw(), BCPostscriptToFile, BCPCLToFile() etc. do not generate any output. Instead they call the active callback function.
When Windows-GDI drawing is started (with BCDraw()) then drawDC, targetDC contain the Windows device contexts (if set).
The parameters x, y, width, and height specify the extent of the barcode row. If drawDC and targetDC are not set then these variables are given in millimeters, where the origin of the coordinate system is the upper, left coordinate of the barcode. The positive X-axis points to the right and the positive Y-axis points downwards.
If drawDC or targetDC are set then the parameters x, y, width, and height use the current logical coordinate system and the logical units of these device contexts.
In your callback function you can use BCGetMetaData() to query the bars and spaces of the current row.
[in,out] | customData | User-defined data. |
[in,out] | barcode | The handle of the barcode. |
[in,out] | drawDC | The device context. |
[in,out] | targetDC | The target device context. |
[in] | x | The left coordinate of the row. |
[in] | y | The top coordinate of the row. |
[in] | width | The width of the row. |
[in] | height | The height of the row. |
ErrOk | Everything went fine, and the drawing continues. |
!=ErrOk | Something went wrong, the drawing function returns with the returned error value. |
This callback function can be set with BCSetFuncDrawBar(). When set the drawing functions such as BCDraw(), BCPostscriptToFile, BCPCLToFile() etc. do not generate any output. Instead they call the active callback function. This function is called once for each bar.
When Windows-GDI drawing is started (with BCDraw()) then drawDC contains the Windows device contexts (if set). The variables x, y, width, and height specify the extent of the bar. If drawDC and targetDC are not set then these variables are given in millimeters, where the origin of the coordinate system is the upper, left coordinate of the barcode. The positive X-axis points to the right and the positive Y-axis points downwards.
If drawDC or targetDC are set then the parameters x, y, width, and height use the current logical coordinate system and the logical units of these device contexts.
[in,out] | customData | User-defined data. |
[in,out] | drawDC | The device context. |
[in] | x | The left coordinate of the row. |
[in] | y | The top coordinate of the row. |
[in] | width | The width of the row. |
[in] | height | The height of the row. |
ErrOk | Everything went fine, and the drawing continues. |
!=ErrOk | Something went wrong, the drawing function returns with the returned error value. |
This callback function can be set with BCSetFuncDrawText(). When set the drawing functions such as BCDraw(), BCPostscriptToFile, BCPCLToFile() etc. do not generate any output. Instead they call the active callback function.
When Windows-GDI drawing is started (with BCDraw()) then drawDC contains the Windows device contexts (if set). The variables x, and y specify the position of the barcode text. If drawDC and targetDC are not set then these variables are given in millimeters, where the origin of the coordinate system is the upper, left coordinate of the barcode. The positive X-axis points to the right and the positive Y-axis points downwards.
If drawDC or targetDC are set then the parameters x and y use the current logical coordinate system and the logical units of these device contexts.
[in,out] | customData | User-defined data. |
[in,out] | drawDC | The device context. |
[in] | font | The LOGFONTA structure that defines the font. |
[in] | x | The x-coordinate of the text. Depending on the alignment, the x specifies either the left, the center or the right coordinate of the text. |
[in] | y | The top coordinate of the text. |
[in] | alignment | The horizontal alignment of the text. (The vertical alignment is always 'top'.) |
[in] | text | The output string. |
[in] | numberOfCharacters | The number of characters in text. |
[in] | drawArea | The draw area for the text. |
[in] | textIndex | The index of given text. 0 ... means that given text is the human readable text. >0 ... means that given text is the extra text with given index [1 .. n]. |
ErrOk | Everything went fine, and the drawing continues. |
!=ErrOk | Something went wrong, the drawing function returns with the returned error value. |
This callback function can be set with BCGetFuncDrawRing(). When set the MaxiCode finder drawing functions do not generate any output. Instead they call the active callback function.
When Windows-GDI drawing is started (with BCDraw()) then drawDC contains the Windows device contexts (if set). The variables x, and y specify the position of center of the ring. If drawDC and targetDC are not set then these variables are given in millimeters, where the origin of the coordinate system is the upper, left coordinate of the barcode. The positive X-axis points to the right and the positive Y-axis points downwards.
If drawDC or targetDC are set then the parameters x and y use the current logical coordinate system and the logical units of these device contexts.
[in,out] | customData | User-defined data. |
[in,out] | drawDC | The device context. |
[in] | x | The x-coordinate (=horizontal) of the ring center. |
[in] | y | The y-coordinate (=vertical) of the ring center. |
[in] | rInner | The radius of the inner margin of the ring. |
[in] | rOuter | The radius of the outer margin of the ring. |
ErrOk | Everything went fine, and the drawing continues. |
!=ErrOk | Something went wrong, the drawing function returns with the returned error value. |
This callback function can be set with BCSetFuncDrawHexagon(). When set the MaxiCode hexagon drawing functions do not generate any output. Instead they call the active callback function.
When Windows-GDI drawing is started (with BCDraw()) then drawDC contains the Windows device contexts (if set). The variables x, and y specify the position of the center of the hexagon. If drawDC and targetDC are not set then these variables are given in millimeters, where the origin of the coordinate system is the upper, left coordinate of the barcode. The positive X-axis points to the right and the positive Y-axis points downwards.
If drawDC or targetDC are set then the parameters x and y use the current logical coordinate system and the logical units of these device contexts.
[in,out] | customData | User-defined data. |
[in,out] | drawDC | The device context. |
[in] | points_x | An array of the 6 x-positions of the hexagon corners (clockwise). |
[in] | points_y | An array of the 6 y-positions of the hexagon corners (clockwise). |
ErrOk | Everything went fine, and the drawing continues. |
!=ErrOk | Something went wrong, the drawing function returns with the returned error value. |