This shows you the differences between two versions of the page.
— |
c:graphics.h:getvisualpage [2024/02/16 01:05] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ===== getvisualpage ===== | ||
+ | |||
+ | |||
+ | ====Syntax of getvisualpage ==== | ||
+ | <code c> | ||
+ | #include "graphics.h" | ||
+ | int getvisualpage(void); | ||
+ | </code> | ||
+ | |||
+ | |||
+ | ==== Description of getvisualpage ==== | ||
+ | <code c> | ||
+ | The getvisualpage function is available in the winbgim implementation of | ||
+ | BGI graphics. getvisualpage gets the page number of the currently visable | ||
+ | page (which is visible on the screen). | ||
+ | The visual graphics page might not be the one where drawing currnetly | ||
+ | takes place. | ||
+ | The original winbgi was designed to support up to 16 pages, but I have | ||
+ | only used pages 1 and 2 myself. NOTE: Using page number 0 might mess up | ||
+ | the colors. I use pages 1-2 for double buffering. | ||
+ | </code> | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ==== See also ==== | ||
+ | [[getactivepage]] | ||
+ | [[setvisualpage]] | ||
+ | [[swapbuffers]] | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ===== output of getvisualpage example ===== | ||
+ | |||
+ | no output of example at the moment | ||
+ | do not hesitate and add it... | ||
+ | |||
+ | |||