Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

render_scene(3alleg4) [opendarwin man page]

render_scene(3alleg4)						  Allegro manual					     render_scene(3alleg4)

NAME
render_scene - Renders all the queued scene polygons. Allegro game programming library. SYNOPSIS
#include <allegro.h> void render_scene(); DESCRIPTION
Renders all the specified scene_polygon3d()'s on the bitmap passed to clear_scene(). Rendering is done one scanline at a time, with no pixel being processed more than once. Note that between clear_scene() and render_scene() you shouldn't change the clip rectangle of the destination bitmap. For speed reasons, you should set the clip rectangle to the minimum. Note also that all the textures passed to scene_polygon3d() are stored as pointers only and actually used in render_scene(). SEE ALSO
create_scene(3alleg4), clear_scene(3alleg4), destroy_scene(3alleg4), scene_gap(3alleg4), scene_polygon3d(3alleg4), exscn3d(3alleg4) Allegro version 4.4.2 render_scene(3alleg4)

Check Out this Related Man Page

scene_polygon3d(3alleg4)					  Allegro manual					  scene_polygon3d(3alleg4)

NAME
scene_polygon3d, scene_polygon3d_f - Puts a polygon in the scene rendering list. Allegro game programming library. SYNOPSIS
#include <allegro.h> int scene_polygon3d(int type, BITMAP *texture, int vc, V3D *vtx[]); int scene_polygon3d_f(int type, BITMAP *texture, int vc, V3D_f *vtx[]); DESCRIPTION
Puts a polygon in the rendering list. Nothing is really rendered at this moment. Should be called between clear_scene() and render_scene(). Arguments are the same as for polygon3d(), except the bitmap is missing. The one passed to clear_scene() will be used. Unlike polygon3d(), the polygon may be concave or self-intersecting. Shapes that penetrate one another may look OK, but they are not really handled by this code. Note that the texture is stored as a pointer only, and you should keep the actual bitmap around until render_scene(), where it is used. Since the FLAT style is implemented with the low-level hline() function, the FLAT style is subject to DRAW_MODEs. All these modes are valid. Along with the polygon, this mode will be stored for the rendering moment, and also all the other related variables (color_map pointer, pattern pointer, anchor, blender values). The settings of the CPU_MMX and CPU_3DNOW flags of the cpu_capabilities global variable on entry in this routine affect the choice of low- level asm routine that will be used by render_scene() for this polygon. RETURN VALUE
Returns zero on success, or a negative number if it won't be rendered for lack of a rendering routine. SEE ALSO
create_scene(3alleg4), clear_scene(3alleg4), render_scene(3alleg4), destroy_scene(3alleg4), polygon3d(3alleg4), cpu_capabilities(3alleg4), exscn3d(3alleg4) Allegro version 4.4.2 scene_polygon3d(3alleg4)
Man Page

2 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Shopt -s histappend

What is the point of this? Whenever I close my shell it appends to the history file without adding this. I have never seen it overwrite my history file. # When the shell exits, append to the history file instead of overwriting it shopt -s histappend (3 Replies)
Discussion started by: cokedude
3 Replies

2. OS X (Apple)

Undeletable file

Greetings, I'm trying to delete a file with a weird name from within Terminal on a Mac. It's a very old file (1992) with null characters in the name: ␀␀Word Finder® Plus™. Here are some examples of what I've tried: 12FX009:5 dpontius$ ls ␀␀Word Finder® Plus™ 12FX009:5 dpontius$ rm... (29 Replies)
Discussion started by: dpontius
29 Replies

Featured Tech Videos