Mercurial > sdl-ios-xcode
view docs/man3/SDL_VideoInfo.3 @ 2884:9dde605c7540
Date: Fri, 19 Dec 2008 20:17:35 +0100
From: Couriersud
Subject: Re: Aw: Experience using SDL1.3 in sdlmame/Proposal for api additions
> For consistency you'd probably want:
> SDL_SetRenderDrawColor(Uint8 r, Uint8 g, Uint8 b, Uint8 a);
> SDL_SetRenderDrawBlendMode(SDL_BlendMode blendMode);
> SDL_RenderLine(int x1, int y1, int x2, int y2);
> SDL_RenderFill(SDL_Rect *rect);
>
> You probably also want to add API functions query the current state.
>
I have implemented the above api for the opengl, x11, directfb and
software renderers. I have also renamed *TEXTUREBLENDMODE* constants to
BLENDMODE*. The unix build compiles. The windows renderer still needs to
be updated, but I have no windows development machine at hand. Have a
look at the x11 renderer for a sample.
Vector games now run at 90% both on opengl and directfb in comparison to
sdlmame's own opengl renderer. The same applies to raster games.
The diff also includes
a) Changed XDrawRect to XFillRect in x11 renderer
b) A number of changes to fix blending and modulation issues in the
directfb renderer.
author | Sam Lantinga <slouken@libsdl.org> |
---|---|
date | Sat, 20 Dec 2008 12:00:00 +0000 |
parents | 546f7c1eb755 |
children | 1238da4a7112 |
line wrap: on
line source
.TH "SDL_VideoInfo" "3" "Tue 11 Sep 2001, 23:01" "SDL" "SDL API Reference" .SH "NAME" SDL_VideoInfo \- Video Target information .SH "STRUCTURE DEFINITION" .PP .nf \f(CWtypedef struct{ Uint32 hw_available:1; Uint32 wm_available:1; Uint32 blit_hw:1; Uint32 blit_hw_CC:1; Uint32 blit_hw_A:1; Uint32 blit_sw:1; Uint32 blit_sw_CC:1; Uint32 blit_sw_A:1; Uint32 blit_fill; Uint32 video_mem; SDL_PixelFormat *vfmt; } SDL_VideoInfo;\fR .fi .PP .SH "STRUCTURE DATA" .TP 20 \fBhw_available\fR Is it possible to create hardware surfaces? .TP 20 \fBwm_available\fR Is there a window manager available .TP 20 \fBblit_hw\fR Are hardware to hardware blits accelerated? .TP 20 \fBblit_hw_CC\fR Are hardware to hardware colorkey blits accelerated? .TP 20 \fBblit_hw_A\fR Are hardware to hardware alpha blits accelerated? .TP 20 \fBblit_sw\fR Are software to hardware blits accelerated? .TP 20 \fBblit_sw_CC\fR Are software to hardware colorkey blits accelerated? .TP 20 \fBblit_sw_A\fR Are software to hardware alpha blits accelerated? .TP 20 \fBblit_fill\fR Are color fills accelerated? .TP 20 \fBvideo_mem\fR Total amount of video memory in Kilobytes .TP 20 \fBvfmt\fR \fIPixel format\fR of the video device .SH "DESCRIPTION" .PP This (read-only) structure is returned by \fI\fBSDL_GetVideoInfo\fP\fR\&. It contains information on either the \&'best\&' available mode (if called before \fI\fBSDL_SetVideoMode\fP\fR) or the current video mode\&. .SH "SEE ALSO" .PP \fI\fBSDL_PixelFormat\fR\fR, \fI\fBSDL_GetVideoInfo\fP\fR ...\" created by instant / docbook-to-man, Tue 11 Sep 2001, 23:01