Inputs/actions processed out of order when starting a torrent and then moving down

[Soundtoxin]

I added two torrents in a stopped state, then manually set their file paths. I wanted to start one before the other. I press ts to start the torrent. Then I press j to go down, planning to start the second torrent in a few seconds once I make sure the first is downloading. Somehow the second torrent that I moved down to is the one that got started. I quickly stop it, wait a second, move up, and start the one I meant to start.

stig version 0.12.1a0 I have 1874 torrents in this transmission instance, which may affect performance and make this problem more likely.

[rndusr]

Yes, unfortunately, stig is full of race conditions.