Ed Leafe wrote: > On Nov 8, 2008, at 1:24 PM, Bob Sysero llc Dev wrote: > > >> I am not using import sys anywhere in my Form but to get arround the >> problem is there away that I could set the sys.stdout to the command >> screen? >> > > You could try working with <shell>.interp.stdout, where <shell> is > the command window. You can't use 'self', since 'self' is mapped to > the window that was active when the command window was opened. > > > -- Ed Leafe > Before looking into the <shell>.interp.stdout in the command window I tried running my Form in the Class Designer. While the form is running I selected File -> Command Window. I am able to type print 4 + 4 while my Form is running in the background and in the butom split screen the output was 8. When I pressed the button to trigger the onHit then my dabo.trace() is called and then there is no output to the spite screen. I even have in my code:
def onHit(self, evt): Buttons = 3 print Buttons dabo.trace() self.Form.QuickButton1.Caption ="ORDER" self.Form.QuickButton1.FontBold = True self.Form.QuickButton1.refresh() The print Buttons is not even printing to the command window split screen to show me the number 3. I pressed n the q to quit followed by the enter key then I received a message in the split screen. I can enter print 2 + 4 and the split screen will display 6 again. This is the top command window: __________________________________________________________________________ Python 2.5.2 (r252:60911, Jul 31 2008, 17:31:22) [GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)] on linux2 Type "help", "copyright", "credits" or "license" for more information. print 4 + 4 (Pdb) n (Pdb) q Print 2 + 5 print 2 + 4 ___________________________________________________________________________ Bottom split screen _______________________________________________ 8 Traceback (most recent call last): File "<input>", line 1, in <module> NameError: name 'q' is not defined File "<input>", line 1 Print 2 + 5 ^ SyntaxError: invalid syntax 6 ________________________________________________ The lines: Traceback (most recent call last): File "<input>", line 1, in <module> NameError: name 'q' is not defined came from the pdb on exit. I even removed the dabo.trace() out to see If the print Buttons would print to the command window split screen and again no output in the split screen. I think the problem is within the onHit dButton1 object in the Class Designer. Does dabo have a dabo.interp.stdout so I can send the print Buttons local variable that was set to 3 to the command split screen? I think if I get that fixed that should fix the pdb problem? Another debugger that is explained in the FrontPage wiki about the Winpdb <http://dabodev.com/wiki/WinPDB> debugger have something simular to the dabo.trace()? Bob _______________________________________________ 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]
