Thank you for all of the helpful information. In the spirit of helping the ClassDesigner get more reliable, I compiled a list of smaller issues that I've come across. Based on previous discussions, it sounded like this is the best way to deal with this sort of thing. If I should be posting these in Trac, let me know.
Thanks, Richard Esplin ---- Selecting File->Save as Class in the class designer causes a segmentation fault. (I logged this one in Trac last week #1171). Ending Form-code.py with a comment causes a syntax error at runtime. (I logged this one in Track last week #1172). Opening ClassDesigner with a non-existing filename that does not end in .cdxml apperas to work fine, but clicking save doesn't create the file. The <filename>-code file is created however. I would expect that it would just append .cdxml and save. Opening ClassDesigner with a non-existing filename that does end in .cdxml works, but the Properties Grid in the Object Info dialog has each row at a maximum height so that it is unusable. The arrows on the scroll bar are non-responsive in this state. Shft+Ctrl+R doesn't run the application, even though it's the listed shortcut in File->Run. On Saturday 04 October 2008 08:45:18 Ed Leafe <[EMAIL PROTECTED]> wrote: <snip> > Many Dabo users still hand-code, mainly because they started before > the Class Designer was mature enough to be reliable. That's > unfortunate, because the only way for it to get better is for lots of > different developers using it in different ways and uncovering those > hidden bugs. <snip> > -- Ed Leafe _______________________________________________ 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]
