Ed Leafe wrote: > You can add code to hide, show, resize, and change any property of > any control that you want, just the same as with any other Python GUI > program. Once the .cdxml is converted to your objects, they're regular > objects, and can be manipulated as you like. > > > There is also the online docs that are generated similarly: > http://paul.dabodev.com/doc/api/dabodoc/ > > > I would strongly advise not to rely on the generated code. This code > is constantly being improved, and what it generates today may be > different than what it generates in the future. It is also rather > inefficient, as it sacrifices efficiency for flexibility. > > > I don't think this is a good idea. The code that it generates is > completely dependent on Dabo, so there is no way you could access it > in other modules without also importing the dabo module. If you're > importing dabo, you might as well use it as it was designed. > > > It is not dPanel; it's the base dForm class that has its MenuBarClass > set to dBaseMenuBar. In your form, if you don't want a menu created, > set that property to None. > > -- Ed Leafe > > > > > [excessive quoting removed by server]
_______________________________________________ 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]
