CEGUI (Crazy Eddie's GUI) Forums

Hi ,

I can't exactly figure out how to get the mouse event data. I'm passing data from a Lua event to the C++ function. I can get the window data, but not the mouse data.

Notw: I'm using the "Clicked" which is set by a property in the XML layout file.

LUA:


Declaration BuildItemClick:



Casting code:



The last two ones work. The MouseEventArgs are not initialized at all and contain a lot of junk data. I've searched the entire CEGUI solution collection, but no luck in finding an example.

Any idea?


---

hm, I just realized that this is the incorrect forum. Hm, oh well

The push button "Clicked" event handler is passed a WindowEventArgs& which is not a MouseEventArgs& so attempting to cast to that is an illegal cast.

You'd have to let us know exactly what you're doing so we could advise on how to get the information you're after.

Hm. I want to which button was pressed for the "click" event, and possibly the scrollwheel as well (just a usability thing). Since this was the 'clicked' event I assume it had MouseEvent args as well. (Which looked a bit obvious to me)

the "Clicked" event only occurs on the left button.
you can't really get much info other that the window clicked!

Hm, I didn't know that. I'll check out an alternative, (probably a simple left/right click function which call the same function but with a different argument, unless I similar click event which does do both) Thanks!

There is a "MouseClick" event, which is fired for all buttons, although this functions at a lower level that the button (so has slightly different logic), but it might be worth playing with

Yeah, I'm using the MouseUp event now. Seems to work just as well as Clicked(). Right now I'm onto the placing of objects onto the terrain .

btw, I was wondering. If I have a default window, the root element, which is (ofcourse) the full window size. If I put a scrollwheel handler on that, will it trigger as well when there is a child window under the mouse?

So:


So, if I perform a scrollwheel event above the button, will the root still get the event?

And what if the root has a MouseUp event, and a button as well. Will the event follow the hierarchy or not? If so, then I makes things quite easier to have only one MouseEvent system instead of having two (one for the interface, and one for the "in game 3D stuff".

Just wondering

Most injected events that are not somehow consumed by a widget, eventually find their way back to the root window, so you should indeed be able to do what you want