I'm sorry that the problem proved so troublesome. I had hoped it would be as painless as the last couple.
There are three border sizers in that form. I added two of them through the UI normally. The third (the furthest to the right) I first added within the scrollpanel and I decided that I didn't like it there. Rather than recreating everything, I moved it in the XML file to look like the other two sizers. I was able to reproduce the problem with the cdxml before I edited it, so I thought that I had eliminated my hand-tweak as the source of the problem. I did a lot of playing with various controls in the UI, and I probably messed something up. Thank you for your help. I'm trying to rethink the application so that the UI isn't so painful. My users need to see a lot of information at once. I can eliminate the border sizers if they are what are causing the problems. How did you trace it to the border sizer? Is there some way to enable logging, or to get enough information to debug this on my own? Do you use pdb or PyDev? Also, is there any current documentation on hand-coding dabo interfaces? Thank you again, Richard Esplin On Friday 03 October 2008 20:13:48 Ed Leafe <[EMAIL PROTECTED]> wrote: > On Oct 3, 2008, at 8:11 PM, Ed Leafe wrote: > > OK, I've tracked it down to an incorrect class being recorded. The > > border sizer creates a box, but that box is being saved in the cdxml > > file, which is incorrect. Let me dig a little more and see what I need > > to do to fix this. > > Wow. First off, let me say that this is the most complex form I've > seen in a while! It took a while to finally load; for a time I thought > that it had hung! > > Once I commented out the line that creates the dBox (line #39), the > form loaded correctly, albeit slowly. I thought that perhaps the box > sizer had caused a dBox control to be saved, but I've just tried > creating several forms with border sizers, and none of them created a > dBox entry in the .cdxml file. I thought that perhaps you added the > box directly, but that would not have been possible, as the box was > not contained in any sizer (which was the cause of the error you saw). > > I know that this is a very complex form, but do you remember anything > about when you created that border sizer that seemed odd? I can't seem > to reproduce the problem. > > -- Ed Leafe > <snip> _______________________________________________ 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]
