Ed Leafe wrote: > On Nov 8, 2008, at 3:44 PM, Bob Sysero llc Dev wrote: > > >> 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? >> > > Dabo doesn't mess with sys.stdout at all. The command window, which > is basically the dShell control, which is basically the py.shell, has > its own output. > > If you call the code from the shell/command window, the output should > be in the shell. If you run the code by interacting with the form, the > output should be in the terminal window from which you launched the app. > > > -- Ed Leafe First of all Ed I like to thank you for the help with this major issue that I was at a complete lost on how to solve. When you send the "output should be in the terminal window" I decided to manual run the ClassDesigner in the termianl window. When I ran the dabo.trace() works but the output is not in the command split window but in the terminal window displays all the pdb data. At least this is a workaround that works. Back to my project.
Thank you 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]
