On Monday 08 September 2008 02:57:29 pm johnf wrote: > On Monday 08 September 2008 02:48:52 pm Paul McNett wrote: > > johnf wrote: > > > On Monday 08 September 2008 02:14:26 pm johnf wrote: > > >> On Monday 08 September 2008 02:05:44 pm Paul McNett wrote: > > >>> dabo.ui.yieldUI() > > >> > > >> Oh yea! Thanks at least now I'm getting some sort of update. I > > >> continue testing. > > > > > > I guess I spoke to soon. It appears that it works only the first time. > > > > In addition to calling refresh() before the yieldUI(), check your > > sourcecode. In the code you posted, you've never defined the Range of > > the gauge, which means it'll get the default Range of 100. > > Yes I did not set the Range. Even when I set it to 2 I only get half of > the gauge to work > > > I tried running your code, but it relied on too much external stuff. I'd > > suggest trying to create a small sample that uses dummy data and a dummy > > counter to make sure you can get *that* gauge to work. Then, add the ftp > > callback. > > > > Paul > > OK I see if I can just get the gauge to work without the ftp. What about > use the status bar?
OK it looks like I discovered my problem. However, I need someone to explain why my old code did not work. What appears to be not working was self.thegauge.Value=+1 but self.thegauge.Value = var number that continues to get larger worked. This tells me that python was always setting the gauge value to 1 instead of adding 1 to the current value. Can someone explain how that happened? -- 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]
