Re: [ocemp-devel] OcempGUI unstable rendering patch #2

[Marcus v. A. <ma...@sy...>]

On, Mon Feb 27, 2006, Benjamin Olsen wrote:

> > Right, this is not possible without some effort at the moment, as it
> has
> > to be specified on which layer the object should reside. Possibly an
> > additional 'catchall' EventManager for the Renderer should be added,
> > which is used to distribute the events to additional objects in the
> > first place.
> > Of course one could use an own additional EventManager, but that would
> > cause her to implement an own event loop. So I guess adding an
> > additional EventManager in the first place to the Renderer would be
> > sufficient here, not?
>=20
> Well, the Renderer already has a default EventManager on layer[0],
> right? I think it would be simpler to make the 'catchall' just linked to
> this default layer's EventManager. Is that possible?
>=20

Of course it is. I just wonder, if that is the right approach as the
object then would depend completely on the layer. This could cause it to
be not informed, if e.g. an event is sent to the previous layer and then
set as handled. As the Renderer will stop passing that event around this
could inflict some unwanted side effects on that object.

Thus an independant Renderer or maybe an own slot to bind (an) additional
EventManager(s) to it would allow more flexibility. Or do I miss
something here?

Regards
Marcus