Differences
This shows you the differences between two versions of the page.
en:software:qview:qview_6:qcl_library:vi10drawbuffer [2017/02/27 17:35] – created qem103 | en:software:qview:qview_6:qcl_library:vi10drawbuffer [2019/08/29 17:01] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== VI10DrawBuffer ====== | ||
+ | |||
+ | **V = **// | ||
+ | |||
+ | **I = **//Image// | ||
+ | |||
+ | Function that is used to manage the Vector Image feature (object that resides on some versions of Qpaint). | ||
+ | |||
+ | The VI10DrawBuffer function asks at the HMI device to process and draw, the contents of the buffer. Processing content buffer is not a synchronous operation to the execution of the function, so that means with the VI10DrawBuffer function you report only to a HMI device buffer to be processed. Will be the HMI and so the the firmware, decide how and when to start the design phase.\\ | ||
+ | In order to understand when the drawing operation is completed and you can create a new drawing buffer you must use the VI10WaitBufferReadyUsingEND or VI10WaitBufferReadyUsingWAIT functions. | ||
+ | |||
+ | ===== IMPLEMENTATION ===== | ||
+ | |||
+ | **VI10DrawBuffer (awBuffer)** | ||
+ | |||
+ | Parameters: | ||
+ | |||
+ | ^IN/ | ||
+ | | IN | ARRSYS /\\ ARRGBL | ||
+ | |||
+ | === Example === | ||
+ | |||
+ | //TASK_00// | ||
+ | <code QCL> | ||
+ | MAIN: | ||
+ | IF gfDraw | ||
+ | VI10DrawBuffer (awBuffer) ; | ||
+ | gfDraw = 0 | ||
+ | ENDIF | ||
+ | END | ||
+ | </ | ||
+ | |||
+ | === Note === | ||