A bit confused about Stopping all existing threads in stopDelegation

[DelusionArun]

I am a bit confused about what stopping all existing threads means? When startDelegation runs the very first time, the Thread Activecount is 6. Are we supposed to stop them?

[Troublor]

#10
Is this discussion useful to you?

[DelusionArun]

Is the first one (only stopping those created from startDelegation) the right approach?

[Troublor]

Well, thread is only created by startDelegation, so stopDelegation should stop the thread created by the startDelegation of the same Robot instance (the robot itself). The rationale behind is that one robot instance can only have one thread at the same time.

[DelusionArun]

Thanks for clarifying my doubts

[MeteorTony]

I am still confused, so startDelegation() should call stopDelegation() to stop its own robot thread before it creates its own robot thread? But before the first thread is created, there is no robot thread to be stopped?
Is there any way to check the correctness of stopDelegation? In my implementation, even if I didn't write any codes in stopDelegation(), the game seems to still proceed normally. I have thought of some ways to test the correctness, like originally before creating any robot thread the active thread count is 6, after creating 2 robot threads, the count is 8. When the game ends and starts again, the active thread count becomes 6 again...

[Troublor]

I am still confused, so startDelegation() should call stopDelegation() to stop its own robot thread before it creates its own robot thread? But before the first thread is created, there is no robot thread to be stopped?

If there is no thread, then it is fine. The initial design is that the robot may be started and stopped many times.

Is there any way to check the correctness of stopDelegation?

You can check the thread state (TERMINATED state) to tell whether the thread has been stopped or not.