Yes, I was thinking of the kill kommand. The OP stated that the jobs are "triggered successfully one after another", which led me to the assumption that they are somehow put into a queue, and Tk::ExecuteCommand of the second job is done only after the first has completed. At least this would be an explanation for the reported behaviour.
I think we need more info (source) from Janish to be able to help.
In reply to Re^5: Kill a serial of jobs with a button click in Perl/TK
by soonix
in thread Kill a serial of jobs with a button click in Perl/TK
by Janish
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |