Everything in the Irrlicht Engine can be found in this namespace. More...
Basic classes such as vectors, planes, arrays, lists, and so on can be found in this namespace.
The gui namespace contains useful classes for easy creation of a graphical user interface.
This namespace provides interfaces for input/output: Reading and writing files, accessing zip archives, xml files, ...
All scene management can be found in this namespace: Mesh loading, special scene nodes like octrees and billboards, ...
The video namespace contains classes for accessing the video driver. All 2d and 3d rendering is done here.
Everything in the Irrlicht Engine can be found in this namespace.
As of Irrlicht 1.6, position2d is a synonym for vector2d.
You should consider position2d to be deprecated, and use vector2d by preference.
|typedef char irr::c8|
|typedef float irr::f32|
|typedef double irr::f64|
|typedef char irr::fschar_t|
Type name for character type used by the file system.
Should the wide character version of the FileSystem be used it is a 16 bit character variable. Used for unicode Filesystem and unicode strings. Else it is a 8 bit character variable. Used for ansi Filesystem and non-unicode strings
|typedef IrrlichtDevice* IRRCALLCONV* irr::funcptr_createDevice(video::E_DRIVER_TYPE deviceType, const core::dimension2d< u32 > &windowSize, u32 bits, bool fullscreen, bool stencilbuffer, bool vsync, IEventReceiver *receiver)|
|typedef IrrlichtDevice* IRRCALLCONV* irr::funcptr_createDeviceEx(const SIrrlichtCreationParameters ¶meters)|
|typedef signed short irr::s16|
|typedef signed int irr::s32|
|typedef long long irr::s64|
|typedef signed char irr::s8|
|typedef unsigned short irr::u16|
|typedef unsigned int irr::u32|
|typedef unsigned long long irr::u64|
|typedef unsigned char irr::u8|
An enum for the different device types supported by the Irrlicht Engine.
A device native to Microsoft Windows.
This device uses the Win32 API and works in all versions of Windows.
A device native to Windows CE devices.
This device works on Windows Mobile, Pocket PC and Microsoft SmartPhone devices
A device native to Unix style operating systems.
This device uses the X11 windowing system and works in Linux, Solaris, FreeBSD, OSX and other operating systems which support X11.
A device native to Mac OSX.
This device uses Apple's Cocoa API and works in Mac OSX 10.2 and above.
A device which uses Simple DirectMedia Layer.
The SDL device works under all platforms supported by SDL but first must be compiled in by defining the IRR_USE_SDL_DEVICE macro in IrrCompileConfig.h
A device for raw framebuffer access.
Best used with embedded devices and mobile systems. Does not need X11 or other graphical subsystems. May support hw-acceleration via OpenGL-ES for FBDirect
A simple text only device supported by all platforms.
This device allows applications to run from the command line without opening a window. It can render the output of the software drivers to the console as ASCII. It only supports mouse and keyboard in Windows operating systems.
This selection allows Irrlicht to choose the best device from the ones available.
If this selection is chosen then Irrlicht will try to use the IrrlichtDevice native to your operating system. If this is unavailable then the X11, SDL and then console device will be tried. This ensures that Irrlicht will run even if your platform is unsupported, although it may not be able to render anything.
Enumeration for all event types there are.
An event of the graphical user interface.
GUI events are created by the GUI environment or the GUI elements in response to mouse or keyboard events. When a GUI element receives an event it will either process it and return true, or pass the event to its parent. If an event is not absorbed before it reaches the root element then it will then be passed to the user receiver.
A mouse input event.
Mouse events are created by the device and passed to IrrlichtDevice::postEventFromUser in response to mouse input received from the operating system. Mouse events are first passed to the user receiver, then to the GUI environment and its elements, then finally the input receiving scene manager where it is passed to the active camera.
A key input event.
Like mouse events, keyboard events are created by the device and passed to IrrlichtDevice::postEventFromUser. They take the same path as mouse events.
A joystick (joypad, gamepad) input event.
Joystick events are created by polling all connected joysticks once per device run() and then passing the events to IrrlichtDevice::postEventFromUser. They take the same path as mouse events. Windows, SDL: Implemented. Linux: Implemented, with POV hat issues. MacOS / Other: Not yet implemented.
A log event.
Log events are only passed to the user receiver if there is one. If they are absorbed by the user receiver then no text will be sent to the console.
A user event with user data.
This is not used by Irrlicht and can be used to send user specific data though the system. The Irrlicht 'window handle' can be obtained from IrrlichtDevice::getExposedVideoData() The usage and behavior depends on the operating system: Windows: send a WM_USER message to the Irrlicht Window; the wParam and lParam will be used to populate the UserData1 and UserData2 members of the SUserEvent. Linux: send a ClientMessage via XSendEvent to the Irrlicht Window; the data.l and data.l members will be casted to s32 and used as UserData1 and UserData2. MacOS: Not yet implemented
This enum is never used, it only forces the compiler to compile these enumeration values to 32 bit.
enumeration for key actions. Used for example in the FPS Camera.
This value is not used. It only forces this enumeration to compile in 32 bit.
Possible log levels. When used has filter ELL_DEBUG means => log everything and ELL_NONE means => log (nearly) nothing. When used to print logging information ELL_DEBUG will have lowest priority while ELL_NONE messages are never filtered and always printed.
Used for printing information helpful in debugging.
Useful information to print. For example hardware infos or something started/stopped.
Warnings that something isn't as expected and can cause oddities.
Something did go wrong.
Logs with ELL_NONE will never be filtered. And used as filter it will remove all logging except ELL_NONE messages.
Enumeration for all mouse input events.
Left mouse button was pressed down.
Right mouse button was pressed down.
Middle mouse button was pressed down.
Left mouse button was left up.
Right mouse button was left up.
Middle mouse button was left up.
The mouse cursor changed its position.
The mouse wheel was moved. Use Wheel value in event data to find out in what direction and how fast.
Left mouse button double click. This event is generated after the second EMIE_LMOUSE_PRESSED_DOWN event.
Right mouse button double click. This event is generated after the second EMIE_RMOUSE_PRESSED_DOWN event.
Middle mouse button double click. This event is generated after the second EMIE_MMOUSE_PRESSED_DOWN event.
Left mouse button triple click. This event is generated after the third EMIE_LMOUSE_PRESSED_DOWN event.
Right mouse button triple click. This event is generated after the third EMIE_RMOUSE_PRESSED_DOWN event.
Middle mouse button triple click. This event is generated after the third EMIE_MMOUSE_PRESSED_DOWN event.
No real event. Just for convenience to get number of events.
|IRRLICHT_API IrrlichtDevice* IRRCALLCONV irr::createDevice||(||video::E_DRIVER_TYPE||deviceType =
|const core::dimension2d< u32 > &||windowSize =
|IEventReceiver *||receiver =
Creates an Irrlicht device. The Irrlicht device is the root object for using the engine.
If you need more parameters to be passed to the creation of the Irrlicht Engine device, use the createDeviceEx() function.
|deviceType,:||Type of the device. This can currently be video::EDT_NULL, video::EDT_SOFTWARE, video::EDT_BURNINGSVIDEO, video::EDT_DIRECT3D8, video::EDT_DIRECT3D9 and video::EDT_OPENGL.|
|windowSize,:||Size of the window or the video mode in fullscreen mode.|
|bits,:||Bits per pixel in fullscreen mode. Ignored if windowed mode.|
|fullscreen,:||Should be set to true if the device should run in fullscreen. Otherwise the device runs in windowed mode.|
|stencilbuffer,:||Specifies if the stencil buffer should be enabled. Set this to true, if you want the engine be able to draw stencil buffer shadows. Note that not all devices are able to use the stencil buffer. If they don't no shadows will be drawn.|
|vsync,:||Specifies vertical syncronisation: If set to true, the driver will wait for the vertical retrace period, otherwise not.|
|receiver,:||A user created event receiver.|
|IRRLICHT_API IrrlichtDevice* IRRCALLCONV irr::createDeviceEx||(||const SIrrlichtCreationParameters &||parameters||)|
Creates an Irrlicht device with the option to specify advanced parameters.
Usually you should used createDevice() for creating an Irrlicht Engine device. Use this function only if you wish to specify advanced parameters like a window handle in which the device should be created.
|parameters,:||Structure containing advanced parameters for the creation of the device. See irr::SIrrlichtCreationParameters for details.|