Can we not process "exit" action?

[hchoaf]

I understand that for each action file, all actions before (and inclusive) the first "Exit" should be processed.

However it seems like processing "Exit" in an inputEngine will trigger shouldStop() to return true. Since we are not supposed to modify other files, I just skipped processing the first "Exit" and modified the code to acquire the same result as processing it. Is this allowed?

[Troublor]

Override the shouldStop method will do the trick.

[chin-fung-luk]

Why do need to override the shouldStop? Whatever there is an Exit action, the program will process the exit and break the while loop. Which means the "Thread" will do nothing.

[hchoaf]

From my understanding, isExitSpecified will be True after an inputEngineRunnable processes exit. Then shouldStop in the other inputEngineRunnables will return True and the actions of other action files will not be processed as isExitSpecified is under the scope of AbstractSokobanGame.

[Troublor]

First, I didn’t say you must override it. I just meant if you want to change the behavior of shouldStop, you can override it.

Second, @chin-fung-luk I suggest you take a closer look at PA3 specification, one exit action from one input engine only stops itself. Other input engine should still keep preforming actions.