On Jun 4, 2007, at 11:45 AM, johnf wrote:

>> 1) This should be posted on dabo-users, not dabo-dev.
>
> Why?  I think there is something wrong at the framework level or  
> lower wxPython.

        Generally, framework design questions go on dabo-dev. Potential bugs  
generally go on dabo-users. If the bug report turns out to uncover a  
design issue with the framework, at that point we move it over to  
dabo-dev.

        What's the difference? There are a lot more subscribers to dabo- 
users, and thus a greater pool of eyes to spot what might be the true  
problem.

>> 2) Liberal print statements help (is the codeblock even running?)
>>
> Yes! It is running.

        I think what Paul means is to debug by adding a print statement at  
each potential branch or test so that you can see that the result is  
what you are expecting.

>> 5) Instead of "white", set the normal background to something like
>> 'blue' so you know if the code block is working or not.  I'm not  
>> getting a color change from self.BackColor = 'blue' although the  
>> line of code does excute (from the debugger).
>
> There is nothing wrong with the re statement.  The line   
> self.BackColor == "pink" does excute just nothing occurs or a  
> better statement is that the color change does not appear.

        I believe that his point was that since the default is white, it  
makes sense while testing to set it to something other than white in  
order to verify that it is/isn't working in that case.

> I'm little confused about how I should explain what is happening.   
> In the past you have asked me to provide code to help explain the  
> problem.  The code is not meant for you to run but a means to  
> explain what I'm doing.  It takes time to provide a running  
> example.  For example if I had said BackColor is not working for  
> me.  You would have said it works for me without some sort of  
> context and I would have agreed.  I guess I will have to provide a  
> test case.

        I have tested this at the wxPython level, and it seems to be a  
behavior in wxPython, not Dabo. I will report it to that list.

        FWIW, I keep a small test program template to which I just add the  
one or two controls I need, along with any code, and use that for my  
examples. I have one for Dabo and one for wxPython, so that I can  
report a problem easily at either level. I've added the Dabo template  
after my sig.

-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
import wx
import dabo
dabo.ui.loadUI("wx")
import dabo.dEvents as dEvents

class TestForm(dabo.ui.dForm):
        def afterInit(self):
                self.Caption = "Example"
                # Add stuff here

def main():
        app = dabo.dApp()
        app.MainFormClass = TestForm
        app.start()

if __name__ == '__main__':
        main()




_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message: http://leafe.com/archives/byMID/dabo-dev/[EMAIL PROTECTED]

Reply via email to