Dustin, I have to agree with the last response. As long as you are calling post_event as opposed to process_event, your reaction looks fine. The issue might not be with this particular reaction. But if somewhere else you are inadvertently calling process_event while responding to a transition, you might be corrupting your state which is only later detected by this assertion. Dan -----Original Message----- From: Boost-users [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Andreas Huber Sent: Friday, June 14, 2013 7:36 To: boost-users@lists.boost.org Subject: Re: [Boost-users] [statechart] state_machinesend_event assertion fails Hi Dustin
boost::statechart::result Container::react(const e_still&)
{
post_event(i_still_action());
post_event(i_still_moving());
return discard_event();
}
I am unsure if these reactions are the cause of the assertion failure, but given that the error message says "Container" is the InitialState, I have to assume so. Given that, I don't see how either Container or GripperPosition are inactive and don't know how to interpret this error. I'd appreciate some guidance.
Your react function looks fine. Do you by any chance directly or indirectly call state_machine::process_event from inside the state-machine (e.g. in- state reaction, transition, entry action, exit action, etc.)? Thanks, Andreas _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users ________________________________ IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.