On 24/03/2010 11:04, Alex Hall wrote:
A daemon... Good idea, and that makes more sense for what the thread
does anyway; it is just a timer, updating a variable by contacting a
server every hour. By the way, just what is the difference between
user32.PostQuitMessage (0) and sys.exit()?
The forme
A daemon... Good idea, and that makes more sense for what the thread
does anyway; it is just a timer, updating a variable by contacting a
server every hour. By the way, just what is the difference between
user32.PostQuitMessage (0) and sys.exit()?
On 3/24/10, Tim Golden wrote:
> On 24/03/2010 10
* Alex Hall:
Hi all,
I have a program with a timer in it, therefore I have multiple
threads.
Is the "therefore..." an inference or independendent information?
If it is an inference then it may not be correct.
For example, timers in a GUI program need not involve additional threads.
My meth
On 24/03/2010 10:43, Alex Hall wrote:
Hi all,
I have a program with a timer in it, therefore I have multiple
threads. My method of exiting by using "user32.PostQuitMessage (0)" no
longer seems to be doing the job since I added the timer. What else do
I have to do to close my program? I say it is
Hi all,
I have a program with a timer in it, therefore I have multiple
threads. My method of exiting by using "user32.PostQuitMessage (0)" no
longer seems to be doing the job since I added the timer. What else do
I have to do to close my program? I say it is not closing because,
before, I would be
