in reply to Re^4: Kill a serial of jobs with a button click in Perl/TK
in thread Kill a serial of jobs with a button click in Perl/TK

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.

  • Comment on Re^5: Kill a serial of jobs with a button click in Perl/TK

Replies are listed 'Best First'.
Re^6: Kill a serial of jobs with a button click in Perl/TK
by Janish (Sexton) on May 26, 2015 at 06:07 UTC

    Thanks Soonix, your guest is right, I only aware that yes, how am I expect the command to kill a job which is still in-queue and not active, that is ridiculous. Thanks for your explanation, I'll need to re-structure my code to run them in-parallel instead.

[reply]

In Section Seekers of Perl Wisdom