view test/README @ 956:4263beff9e38

Date: Mon, 30 Aug 2004 18:20:25 +0200 From: Joost Baas Subject: why call arts artsc? I, and a few other people at the mplayer-docs-mailinglist were wondering why you decided to call arts artsc. I understand usually users have nothing to do with libsdl, just developers, but because you can choose the audio-driver being used by mplayer, one of which is sdl, and you can also choose the sdl subdriver, it is necessary to have a well-known or logical name. artsc is not the logical choice, and it's very hard to look up the right name if you don't know what you're looking for.
author Sam Lantinga <slouken@libsdl.org>
date Fri, 17 Sep 2004 13:25:06 +0000
parents 05c551e5bc64
children 68f2b997758e
line wrap: on
line source


These are test programs for the SDL library:

	testver		Check the version and dynamic loading and endianness
	testtypes	Check to see if the data types are the correct size
	testhread	Hacked up test of multi-threading
	testlock	Hacked up test of multi-threading and locking
	testerror	Tests multi-threaded error handling
	testsem		Tests SDL's semaphore implementation
	testtimer	Test the timer facilities
	loopwave	Audio test -- loop playing a WAV file
	testcdrom	Sample audio CD control program
	testkeys	List the available keyboard keys
	testvidinfo	Show the pixel format of the display and perfom the benchmark
	checkkeys	Watch the key events to check the keyboard
	testwin		Display a BMP image at various depths
	graywin		Display a gray gradient and center mouse on spacebar
	testsprite	Example of fast sprite movement on the screen
	testbitmap	Test displaying 1-bit bitmaps
	testalpha	Display an alpha faded icon -- paint with mouse
	testwm		Test window manager -- title, icon, events
	threadwin	Test multi-threaded event handling
	testgl		A very simple example of using OpenGL with SDL
	testjoystick	List joysticks and watch joystick events
	testoverlay	Tests the software/hardware overlay functionality.
	testoverlay2	Tests the overlay flickering/scaling during playback.