bool StateMachineImp::PostEvent	(	const EventImp &	evt,
		const char *	ptr,
		size_t	siz
	)

With this function commands are posted to the event queue. If the event loop has not yet been started with Run() the command is directly handled by HandleEvent.

Events posted when the state machine is in a negative state or kSM_FatalError are ignored.

A new event is created and its data contents initialized with the specified memory.

Parameters

evt	The event to be posted. The precise contents depend on what the event should be for.
ptr	pointer to the memory which should be attached to the event
siz	size of the memory which should be attached to the event

Returns

false if the event is ignored, true otherwise.

Todo:

• Shell we check for the validity of a command at the current state, too?
• should we also get the output stream as an argument here?

Definition at line 295 of file StateMachineImp.cc.

References fBufferEvents, GetCurrentState(), HandleEvent(), IsRunning(), kSM_FatalError, kYellow, Lock(), MessageImp::Out(), PushEvent(), and UnLock().

{
    if (/*GetCurrentState()<0 ||*/ GetCurrentState()==kSM_FatalError)
    {
        Out() << kYellow << "State<0 or FatalError: Event ignored." << endl;
        return false;
    }

    if (IsRunning() || fBufferEvents)
    {
        Event *event = new Event(evt, ptr, siz);
        //Debug("Posted: "+event->GetName());
        PushEvent(event);
    }
    else
    {
        // FIXME: Is this thread safe? (Yes, because the data is copied)
        // But two handlers could be called at the same time. Do we
        // need to lock the handlers? (Dim + console)
        // FIXME: Is copying of the data necessary?
        const Event event(evt, ptr, siz);
        Lock();
        HandleEvent(event);
        UnLock();
    }
    return true;
}

Here is the call graph for this function: