RISCWORLD 7

home *** CD-ROM | disk | FTP | other *** search

/ RISCWORLD 7 / RISCWORLD_VOL7.iso / Software / Issue4 / SDL / gcc346 / !SDL / man / SDL_Event.3 < prev next >

Wrap

Text File | 2006-09-20 | 6.8 KB | 249 lines

<html> <head> <title>"SDL_Event"("3") manual page</title> </head> <body bgcolor='#efefef' text='black' link='blue' vlink='#551A8B' alink='red'> <a href='#toc'>Table of Contents</a> <h2><a name='sect0' href='#toc0'>Name</a></h2> SDL_Event- General event structure <h2><a name='sect1' href='#toc1'>Structure Definition</a></h2> <pre>CWtypedef union{ Uint8 type; SDL_ActiveEvent active; SDL_KeyboardEvent key; SDL_MouseMotionEvent motion; SDL_MouseButtonEvent button; SDL_JoyAxisEvent jaxis; SDL_JoyBallEvent jball; SDL_JoyHatEvent jhat; SDL_JoyButtonEvent jbutton; SDL_ResizeEvent resize; SDL_ExposeEvent expose; SDL_QuitEvent quit; SDL_UserEvent user; SDL_SywWMEvent syswm; } SDL_Event; </pre> <h2><a name='sect2' href='#toc2'>Structure Data</a></h2> <dl> <dt>type </dt> <dd>The type of event </dd> <dt>active </dt> <dd>Activation event </dd> <dt>key </dt> <dd>Keyboard event </dd> <dt>motion </dt> <dd>Mouse motion event </dd> <dt>button </dt> <dd>Mouse button event </dd> <dt>jaxis </dt> <dd>Joystick axis motion event </dd> <dt>jball </dt> <dd>Joystick trackball motion event </dd> <dt>jhat </dt> <dd>Joystick hat motion event </dd> <dt>jbutton </dt> <dd>Joystick button event </dd> <dt>resize </dt> <dd>Application window resize event </dd> <dt>expose </dt> <dd>Application window expose event </dd> <dt>quit </dt> <dd>Application quit request event </dd> <dt>user </dt> <dd>User defined event </dd> <dt>syswm </dt> <dd>Undefined window manager event </dd> </dl> <h2><a name='sect3' href='#toc3'>Description</a></h2> The SDL_Event union is the core to all event handling is SDL, its probably the most important structure after SDL_Surface. SDL_Event is a union of all event structures used in SDL, using it is a simple matter of knowing which union member relates to which event type. <dl> <dt>Event type </dt> <dd>Event Structure </dd> <dt>SDL_ACTIVEEVENT </dt> <dd>SDL_ActiveEvent </dd> <dt>SDL_KEYDOWN/UP </dt> <dd>SDL_KeyboardEvent </dd> <dt>SDL_MOUSEMOTION </dt> <dd>SDL_MouseMotionEvent </dd> <dt>SDL_MOUSEBUTTONDOWN/UP </dt> <dd>SDL_MouseButtonEvent </dd> <dt>SDL_JOYAXISMOTION </dt> <dd>SDL_JoyAxisEvent </dd> <dt>SDL_JOYBALLMOTION </dt> <dd>SDL_JoyBallEvent </dd> <dt>SDL_JOYHATMOTION </dt> <dd>SDL_JoyHatEvent </dd> <dt>SDL_JOYBUTTONDOWN/UP </dt> <dd>SDL_JoyButtonEvent </dd> <dt>SDL_QUIT </dt> <dd>SDL_QuitEvent </dd> <dt>SDL_SYSWMEVENT </dt> <dd>SDL_SysWMEvent </dd> <dt>SDL_VIDEORESIZE </dt> <dd>SDL_ResizeEvent </dd> <dt>SDL_VIDEOEXPOSE </dt> <dd>SDL_ExposeEvent </dd> <dt>SDL_USEREVENT </dt> <dd>SDL_UserEvent </dd> </dl> <h2><a name='sect4' href='#toc4'>Use</a></h2> The SDL_Event structure has two uses <dl> <dt> </dt> <dd>Reading events on the event queue </dd> <dt> </dt> <dd>Placing events on the event queue </dd> </dl> Reading events from the event queue is done with either SDL_PollEvent or SDL_PeepEvents. We'll use SDL_PollEvent and step through an example. First off, we create an empty SDL_Event structure. <pre>CWSDL_Event test_event; </pre> SDL_PollEvent removes the next event from the event queue, if there are no events on the queue it returns 0 otherwise it returns 1. We use a while loop to process each event in turn. <pre>CWwhile(SDL_PollEvent(&test_event)) { </pre> The SDL_PollEvent function take a pointer to an SDL_Event structure that is to be filled with event information. We know that if SDL_PollEvent removes an event from the queue then the event information will be placed in our test_event structure, but we also know that the type of event will be placed in the type member of test_event. So to handle each event type seperately we use a switch statement. <pre>CW switch(test_event.type) { </pre> We need to know what kind of events we're looking for and the event type's of those events. So lets assume we want to detect where the user is moving the mouse pointer within our application. We look through our event types and notice that SDL_MOUSEMOTION is, more than likely, the event we're looking for. A little more research tells use that SDL_MOUSEMOTION events are handled within the SDL_MouseMotionEvent structure which is the motion member of SDL_Event. We can check for the SDL_MOUSEMOTION event type within our switch statement like so: <pre>CW case SDL_MOUSEMOTION: </pre> All we need do now is read the information out of the motion member of test_event. <pre>CW printf("We got a motion event. "); printf("Current mouse position is: (%d, %d) ", test_event.motion.x, test_event.motion.y); break; default: printf("Unhandled Event! "); break; } } printf("Event queue empty. "); </pre> It is also possible to push events onto the event queue and so use it as a two-way communication path. Both SDL_PushEvent and SDL_PeepEvents allow you to place events onto the event queue. This is usually used to place a SDL_USEREVENT on the event queue, however you could use it to post fake input events if you wished. Creating your own events is a simple matter of choosing the event type you want, setting the type member and filling the appropriate member structure with information. <pre>CWSDL_Event user_event; user_event.type=SDL_USEREVENT; user_event.user.code=2; user_event.user.data1=NULL; user_event.user.data2=NULL; SDL_PushEvent(&user_event); </pre> <h2><a name='sect5' href='#toc5'>See Also</a></h2> SDL_PollEvent, SDL_PushEvent, SDL_PeepEvents <!-- <hr> <a name='toc'>Table of Contents</a> <ul> <li><a name='toc0' href='#sect0'>Name</a></li> <li><a name='toc1' href='#sect1'>Structure Definition</a></li> <li><a name='toc2' href='#sect2'>Structure Data</a></li> <li><a name='toc3' href='#sect3'>Description</a></li> <li><a name='toc4' href='#sect4'>Use</a></li> <li><a name='toc5' href='#sect5'>See Also</a></li> </ul> </body> </html>