On Monday 08 September 2008 01:35:49 pm Nate Lowrie wrote: > On Mon, Sep 8, 2008 at 2:27 PM, johnf <[EMAIL PROTECTED]> wrote: > > On Monday 08 September 2008 01:11:56 pm Ed Leafe wrote: > >> On Sep 8, 2008, at 3:02 PM, johnf wrote: > >> > I'm displaying a dialog with a dGauge. Within the code of the > >> > dialog I'm > >> > setting the dGauge.Value =+ 1 but the display does not refresh as > >> > expected. > >> > >> Maybe your FTP code is blocking? > >> > >> Does dGauge work correctly for you in DaboDemo, or when running > >> dGauge.py itself? > >> > >> > >> -- Ed Leafe > > > > The dGauge works perfectly in DaboDemo. The FTP code has a callback that > > does two things updates the gauge and prints a period to standard out. > > I'm getting the '.' printing on standard out. So I can only assume that > > the gauge got the value change. > > Is the FTP code running in it's own thread? If so, you need to use > dabo.ui.callAfter to set the dGauge because setting it from a non-wx > thread causes issues. > > Nate L.
I'm just using subclass of ftplib. Does ftplib use threads? And I don't see how using callAfter would help if ftplib does use threads because wouldn't the call to update gauge value have to wait until the ftplib finished. ` -- John Fabiani _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
