Hi Seth, Apologies for late reply. I do not think there is any technical obstacle to follow the proposed way. It has never been necessary to let a single event trigger multiple transitions, that is the sole reason why it is implemented that way.
Cheers, Orson On 1/18/19 4:39 AM, Seth Hillbrand wrote: > Anyone have thoughts on this? > > Thanks- > Seth > > Am 2019-01-03 18:07, schrieb Seth Hillbrand: >> Hi Devs- >> >> Quick question for Tom or others familiar with the event handling >> code. In addressing a ratsnest issue[1], I found that the event >> handler will only allow a single action per tool per event. While we >> appear to be able to queue multiple actions (transitions) for a single >> tool event, the RunMainStack() clears the state transitions >> immediately after the first cofunction is set up. >> >> Is there a technical reason that we do not allow multiple state >> transitions for a single event in the same tool? If there is, should >> we set up an assert to catch duplicate event transitions when they are >> queued? >> >> -Seth >> >> [1] https://bugs.launchpad.net/kicad/+bug/1809752 > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
