Irrlicht Engine

i believe you should declare each global variable you are using in each cpp as being extern (ex : "extern int i" for a global "int i" variable)

thanks for the code, it will help me make my skins scalable too when i need to

btw, last time i tested the focus on a editBox was kept even after the element was hidden via a setVisible(false) => is it normal behaviour or a bug ??

you will have to edit the picture you took IRL so it looks good when multiplied side by side on a terrain, but of course you may use them, and lots of game do ! (as long as their graphic orientation allows it -- realistic)

ok, i don't have windows to test it but from what i understood the events are not dealt exactly the same way on windows or linux, thus the (weird) problem :) If my hack still works on windows then the problem is completely solved ^^ and yes i placed the 2 methods well ;) There is also another proble...

you need to instantiate your button before applying methods on it !

=> btntest = new CGButton();

ok, so i better handle them in each of my GUI classes ? it will be indeed more easier for me (and much, much clearer), though i wanted to be sure that it would not be less efficient than one big event receiver

Hi :) i would like to know how the events work with the built in GUI, as each iguielement has a method onEvent.... => are all events re-sent to the whole GUI "tree" ? or are the GUI events the only one who are re-sent ?? (ie, if there is a keyboard event, i hope it isn't sent everywhere in...

addImage uses the original dimension of the texture though, right ?
So even if the image is not a power of 2 it should work... a priori.. ?

@eneru, it's a taste question, but most C++ coding styles don't use this explicitly in cases it is clear. Calling member functions inside other member functions on the same instance is more or less the default case. Instead use of other functions should be made obvious. Like when calling a function...

bitplane wrote: also, i dont think there's any difference between "this->function()" and "function()"

there is no differences, but the first is much clearer i think (more especially for class arguments)

thanks a lot !!

i thought that "0" was considered as the "root parent" (aka its value) and didn't get there was this test to be made to "convert it" if necessary !
have a nice day

i want to create a new IGUIElement which would just draw a background of a certain color, but can't get something to work :s my class def : protected : irr::video::SColor color; public: //! constructor /*! constructor (cf Irrlicht's IGUIElements) \param irr::gui::IGUIEnvironment* environment \param ...

up ! it is a double post, but for the good hopefully as it works now !!! 8) I am posting the code (there is not much really) so others can use it if they experience problems (@Mastiff : don't hesitate to use it too if you want ;) thanks for the original code btw ;)) if (keyState[event.KeyInput.Key] ...

it doesn't work :'( or to be more explicit, it works wonderfully but only for some time, after which the key input handler become mad >.> i did this test : int i = 0; if (eventReceiver.keyPressed('M')) { cout << i << " ... pressed" << endl; } if (eventReceiver.keyDown('M')) { i++; cout << ...