File: al_flip_display.3

package info (click to toggle)
allegro5 2%3A5.0.10-3
  • links: PTS, VCS
  • area: main
  • in suites: jessie, jessie-kfreebsd
  • size: 14,856 kB
  • ctags: 15,948
  • sloc: ansic: 87,540; cpp: 9,693; objc: 3,491; python: 2,057; sh: 829; makefile: 93; perl: 37; pascal: 24
file content (39 lines) | stat: -rw-r--r-- 1,354 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
.TH al_flip_display 3 "" "Allegro reference manual"
.SH NAME
.PP
al_flip_display \- Allegro 5 API
.SH SYNOPSIS
.IP
.nf
\f[C]
#include\ <allegro5/allegro.h>

void\ al_flip_display(void)
\f[]
.fi
.SH DESCRIPTION
.PP
Copies or updates the front and back buffers so that what has been drawn
previously on the currently selected display becomes visible on screen.
Pointers to the special back buffer bitmap remain valid and retain their
semantics as the back buffer, although the contents may have changed.
.PP
Several display options change how this function behaves:
.IP \[bu] 2
With ALLEGRO_SINGLE_BUFFER, no flipping is done.
You still have to call this function to display graphics, depending on
how the used graphics system works.
.IP \[bu] 2
The ALLEGRO_SWAP_METHOD option may have additional information about
what kind of operation is used internally to flip the front and back
buffers.
.IP \[bu] 2
If ALLEGRO_VSYNC is 1, this function will force waiting for vsync.
If ALLEGRO_VSYNC is 2, this function will not wait for vsync.
With many drivers the vsync behavior is controlled by the user and not
the application, and ALLEGRO_VSYNC will not be set; in this case
al_flip_display(3) will wait for vsync depending on the settings set in
the system\[aq]s graphics preferences.
.SH SEE ALSO
.PP
al_set_new_display_flags(3), al_set_new_display_option(3)