The hero should be able to trigger events while the main interpreter is running #331

Zegeri opened this Issue Aug 19, 2014 · 3 comments


None yet

4 participants

Zegeri commented Aug 19, 2014

It's possible for the hero to trigger other touch/collision events while it's being moved by a list of event commands. In fact, the hero can trigger multiple events, but they won't start until the list has been completed. If more than one events have been triggered, they'll run in ascending order of IDs. This means it doesn't matter in which order these events are triggered by the hero. It looks like in this context, the touch/collision triggers are checked right after the hero's move route has been finished.

That might have been a bit confusing, so here's an example.

@fdelapena fdelapena added this to the 0.3 milestone Mar 18, 2015

Added the test case example to emscripten for online testing:
Latest PR:

@fdelapena fdelapena modified the milestone: 0.3.1, 0.3 May 12, 2015
@fdelapena fdelapena removed the 0.3 blocker label May 12, 2015
Ghabry commented May 13, 2015

What do you think about some convention like test_name_of_test or issue_#number.


Looks good the issue_# way for easier access if exist. Updated links for now.

@fdelapena fdelapena added Interpreter and removed Emulation labels May 19, 2015
@fdelapena fdelapena closed this in #542 Aug 25, 2015
@carstene1ns carstene1ns added Events and removed Events Interpreter labels Jul 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment