Irrlicht Engine

To MasterGod: Thanks much, and I might possibly expand it for more advanced features, possibly GUI events/user events. Any idea's are welcome. To prajay.shetty: You should probably be calling: eventReceiver.init(); just after you create the instance of the class. And the problem is probably this: i...

To Game Dude:
Yes for all practical purposes it's now complete, I'll update it if anything in Irrlitch changes.

To olivehehe_03:
You where already able to do that without modifications, I guess I should have stated that, either way works fine.

I have now finished adding support for the mouse X/Y positions and mouse Wheel data.

I narrowed it down to my startEventProcess() function and furthermore I found it was exactly this line "for (int i = 0; i <= KEY_KEY_CODES_COUNT; i++)" the problem was the "<=", I now changed it to "<" and everything works

To change the cursor position:

device->getCursorControl()->setPosition(int x,int y);

There are also more options listed in the Irrlicht API:
http://irrlicht.sourceforge.net/docu/cl ... ntrol.html

Yes, it's texture would be visible with no modifications just like if you opened the texture up in an image editor.

I was working on my keyboard and mouse input class and was going to implement the Mouse coordinates, my problem is that the first four pixels of the X axis of the window are not handled properly with the coordinates I get from the Event structure. The problem is the first pixel is 0, the next is 1, ...

Your welcome I'm glad your problem is fixed

To Arthur: First we need to know, what you are expecting it to do? Another thing that would help is if you give us your full program code to look at. Also are you getting compiler errors? If so what do they say? Currently the only things I can think of that could be wrong are: A) you expect BoxNode ...

I've now added support for the mouse buttons (left,middle,right).

I'll work on the Mouse Wheel and X/Y position features later, I was puking my guts out yesterday

The class is fully functional.
Vitek helped me solve the problem in my last thread.
All unneeded code was also removed.

To Halan:
Your right an enumeration would probably be better, I'll update it later.

This is version 1.2a of the MastEventReceiver event receiver class. Features are: Four Key/Button states: Pressed (occurs once, the first time a key/button is pressed) Down (if the key/button is pressed or down) Released (occurs once, the first time a key/button is released) Up (if the key/button is...

To Ico & Dances: Yeah it is kind of pointless I basically reconstructed this class from another design I had and I kind of left that the way it was. The code for that is now: if (processState == 0) { // if the key is down if (keyState[event.KeyInput.Key] != UP) { keyState[event.KeyInput.Key] = R...

I've been working on a class that is designed to make my life simpler.(aren't they all?) Basically the class is designed to handle keyboard events and give me easy to use functions for 4 types of key events: Key Press (happens only once, the moment the key is pressed) Key Down (whether the key is do...

Thank you all for the help, I understand now. I can also see how this would sometimes be more useful than declaring the variables outside of the switch statement, as the current way discards the variables after they leave the scope. Your also right I am using Code::Blocks with the gcc compiler. Agai...