Irrlicht Engine

Hi guys. I'm working my way up to making a scaling/rotating sprite-type class. After reading the forums extensively on the topic, below is what I came up with. This code can easily scale the image just by changing the billboard size. I have no idea how to make it rotate with the normal billboard ...

Go for it, but you'll have to implement serialisation for vector2d, as it's currently missing.
If someone where to replace all occurrences of position2d with vector2d, wouldn't the serialization code also just have to be changed from position2d to vector2d?

My vote is just for replacing ...

Sorry to bump, but I've come across a more personally compelling reasons to combine vector2d and position2d, or at least to have some of the trigonometry functionality added to position2d...

I'm current working on a project that in one place requires working out whether the mouse is within circular ...

Hi there,

I was wondering if there is a good way to allow mouse over affects in the irrlicht GUI. Normally, when an element is 'focussed' no other elements receive EMIE_MOUSE_MOVED events (particularly, the Hovered element does not).

I *fixed* it by changing the CGUIEnvironment class's ...

Upon reflection, keeping const correctness when you're using pointers and templated data structures is impossible without some really yucky code allowing for example:
list<T *> to be viewable as a const list<const T *>&..
which is actually possible but quite horrible.

I still do believe that the ...

I don't think that the conceptual difference in the directions of the axes actually make a difference in most cases, and you generally wouldn't use the functions that are affected in the gui anyway.

Also, vector2d has --
getAngle() and getAngleTrig()
which handle both types of y axis. (getAngle ...

Is there somewhere to post this suggestion? its not really a 'bug' as such, it just appears to be a bit of a redundancy.

The main conceptual difference I can see is that a vector2d is a point in 2d space and generally would have the y coordinates increasing in an upwards direction.
whereas ...

Is there a good reason for the existence of both vector2d and position2d when vector2d could fulfill all the task that position2d it used for? (other than backwards compatibility)
After all, position2d is effectively just a vector without some of the useful functions.

-- also they theoretically ...

I can agree with not wanting to break everyones code, but I'd have to say that I think const correctness is a very good thing. And I think that virtually all the methods of IGUIElement that I listed could be made const with no effect on code beyond having to add the word const in any overriding ...

Firstly, if there is a better place for me to post this, please tell me, I wasn't perfectly sure. It is technically a bug I figure.

I've noticed quite a number of situations where members of irrlicht classes are not const when they could be (and should be, in my opinion as a noob to Irrlicht):
e.g ...

original image


after draw2DImage ing it to the screen,

It seems that getOriginalSize() is still not working, it is spitting out the size after scaling.

also, i'm using windows xp

Sorry, but it still seems to be having the same trouble (svn 769). I can send an example image if it would be helpful.

I can't find any ways to directly draw an IImage to the screen.

It seems that you have to use
IVideoDriver::createTexture
to make a texture from it and then use
IVideoDriver::draw2DImage
to draw it to the screen

-----

I'm not too experianced, but my suggestion would be to use
IVideoDriver ...

Using IGUIImage results in weird scaling for images that are non power-of-two dimensions when using EDT_BURNINGSVIDEO.

I think that getOriginalSize() isn't working right, it seems to return the same as getSize() and is always a power of two.

Edit: getOriginalSize() gives different results in EDT ...

Thanks guys, I personally went with changing the engine slightly to put this into IGUIElement. :) I can now override this for non-rectangular buttons.

virtual bool isPointInside(const core::position2d<s32> & point) const
{
return AbsoluteClippingRect.isPointInside(point);
}

A further question ...