Confusing job order results in inability to abort current one

Hi,

when a StaxRip instance is running and I start a new instance creating a new project and adding it to the job list, it is placed as first item in the "jobs" menu in the StaxRip instance processing the job, resulting in the inability to abort the currently processed job which disappears from the menu. Anyways, it would make more sense to append the jobs from another instance at the end of the job list rather than on the beginning - this is a little bit confusing.

Dust Signs

-

Changed something here too but didn't really test everything as this would take quite a bit time so I hope it works better now.

Navigation

User login

Poll

Which container do you prefer?
MKV
50%
MP4
21%
AVI
22%
DIVX
7%
Total votes: 110