event loop in multiple places? :S

[j0nte33]

okay, so im writing a super basic engine, with a statemanager.
this is basically what happends right now:

void CEngine::Update()
{
        // Code for event loop, ( close application )
                CStateMachine::GetInstance().Update();
                Draw();
}
 

in GameStateGame, lets say i have a character, i need to do keyboard check for movement.
i can't just make a event loop in GameStateGame. tried it.
Any tips?

there are some solutions i've come up with but i would like some pointers...

solution 1:

(click to show/hide)

Have the loop in GameStateGame , and when a close call happends, tell CEngine.
It surley would work, but imagine having resize calls and more... every gamestate would be filled with code that "doesn't have with the state to do".

solution 2:

(click to show/hide)

Have the Event loop in CEngine. Take all the events, store them in a vector and send it to the gamestate.
this one seems to be the least painfull...

Thankyou 

[kitteh-warrior]

You should only have one event loop that. From there, you can dispatch the events to other class instances the require the event for processing.

CStateMachine::GetInstance().Update();

If this is a singleton (which it looks like), that is typically a bad design.

[Hapax]

i would like some pointers...

You can tell you're still in coding mode when you read that as "I would like to use some pointers..."

[Jesper Juhl]

As others have already said; have one event loop.
Once an event is consumed in the loop you can dispatch it to any subsystem that needs to process it if needed. But you should not poll for events in more than one location - once an event is read by one event loop it will not be available to another, so that can easily get confusing.