On 2/5/07, jean-michel bain-cornu <[EMAIL PROTECTED]> wrote: > >> For this kind of stuff, I'd try to put "self.out.WriteText(string)" in > >> some 'Idle' event, which avoid to fall in focus loops or other objects > >> events management problems not easy to solve. > >> > > > > This doesn't have anything to do with focus loops or otherwise, it's > > because the OP isn't familiar with event based programming. > > > > You're performing a long-running task which is preventing the event > > loop from processing, so your text isn't updating and your application > > is unresponsive. You need to rewrite your task - either do everything > > asynchronously, or use a threaded approach. If you use the thread > > approach, be sure to not call the updates directly, you can use the > > wx.CallAfter mechanism to call gui functions in a threadsafe manner. > > So it is an event management problem. > The event loop is not yet finished when the program want to display > something, potentially initiating a new event loop. >
This is almost totally wrong. There is no "new event loop" involved. The OP is running a long task in the main thread, which is blocking the event loop. When the event loop is blocked, the application will not update and cannot be interacted with. It's that simple. The event loop in a gui application doesn't "finish" until the application exits. > If you don't want to bother with threads, the idle event approach is not > so bad. Put something to display in a buffer, and display it only one > time the gui have nothing else to do. The problem is not putting the text into the control - the OP is mislead by the symptoms. The problem is the task he's perform in addition to the logging, which is a long running task (and in his sample code is represented by time.sleep). The logging issue is a red herring, the real problem is the way he's structured his application, with work blocking the event loop. Until he changes this, nothing about the way he writes to his log is going to fix the problem. > I use it every time I can, and it's very safe and easy to do. > Furthermore, you can still step into the program with a debugger, which > can be tricky if the program uses threads (I'd say impossible, but I > didn't try in fact). > Using idle events for continual calculation actually has several caveats you need to be aware of, and I don't recommend it. A background thread or a timer is generally a better solution. -- http://mail.python.org/mailman/listinfo/python-list
