NAME<\/a> display-mansync<\/b> : sync mode emulation<\/p>\n display-mansync<\/p>\n Helper library for the implementation of SYNC mode on targets which are inherently ASYNC (e.g. X) and require manual flushes of the framebuffer.<\/p>\n A target wishing to use mansync should open mansync with _ggiAddDL() in it\u2019s own GGIopen(). It must pass a pointer to a _ggi_opmansync structure as the argument to _ggiAddDL(), and must define the following macros:<\/p>\n MANSYNC_init(vis) which is supposed to call the functions in _ggi_opmansync respectively.<\/p>\n Mansync provides the following functions:<\/p>\n int _GGI_mansync_init(vis); int _GGI_mansync_start(vis); int _GGI_mansync_ignore(vis); MANSYNC_SETFLAGS(vis,flags) (The above functions return 0 if successful, -1 if not.)<\/p>\n Please see display\/X, display\/aa or display\/tile to see how mansync is used. The functions should be transparent enough.<\/p>\n
SYNOPIS<\/a>
DESCRIPTION<\/a>
ENVIRONMENT VARIABLES<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
SYNOPIS <\/a> <\/h2>\n
DESCRIPTION <\/a> <\/h2>\n
MANSYNC_deinit(vis)
MANSYNC_start(vis)
MANSYNC_stop(vis)
MANSYNC_ignore(vis)
MANSYNC_cont(vis)<\/p>\n
int _GGI_mansync_deinit(vis);
Initialize\/deinitialize mansync for given visual.<\/p>\n
int _GGI_mansync_stop(vis);
Start\/stop mansync handling. (process,thread,etc.)
You don\u2019t need to explicitly call these;
MANSYNC_SETFLAGS does it for you.<\/p>\n
int _GGI_mansync_cont(vis);
Temporarily start\/stop mansync, e.g. during mode set.
It is o.k. to use them even if mansync has not been started.<\/p>\n
mansync management in ggiSetFlags().<\/p>\n