Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #5104 > unrolled thread

Re: NewBie Doubt in Python Thread Programming

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: NewBie Doubt in Python Thread Programming Chris Angelico <rosuav@gmail.com> - 2011-05-11 21:13 +1000

#5104 — Re: NewBie Doubt in Python Thread Programming

On Wed, May 11, 2011 at 7:08 PM, vijay swaminathan <swavijay@gmail.com> wrote:
> Sorry. My intention was not to send out a private message. when I chose
> reply to all, I was confused if this would start as a new thread. so just
> did a reply..

No probs. If you just send your response to the list
python-list@python.org. it'll get to everyone.

> I have developed a GUI based on pyQT4 which has a run button. when I click
> on run, it invokes a command prompt and runs a .bat file.
>
> Till the execution of .bat file is over, I want the run button on the GUI to
> be disabled. so i thought of invoking the command prompt and running the
> .bat file on a thread so that I could monitor the status of the thread
> (assuming that the thread would be active till command prompt is active -
> correct me if I'm wrong).

Yes, but only if you use os.system().

> Any flaw  in the logic? any other better ways of achieving this?
>

You'll find it easier to get an event at the end of it; simply have
another line of code after the os.system() which will reenable the
button.

Chris Angelico

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web