On Mar 1, 2009, at 6:11 PM, Ricardo Aráoz wrote:
> Thanks Ed, tried John's suggestion and they worked. Now I'm trying it
> this way. You see, the way I think about it, I don't really want to
> create a class but use dabo's dForm as it is, and manipulate it. Maybe
> later I will end up subclassing dForm, but not right now.
That sounds an awful lot like a VFP mindset. Classes are simply
objects like anything else in Python; they are quick and easy to use.
It's much cleaner to define your customizations in a class and
instantiate that, rather than create an instance and then try to
change it.
> The corrected program (as per your suggestions) is below. It works ok,
> but besides the form, there is a "Dabo Application" window created
> with
> the default menu. After I close my form the application window
> persists,
> if I close the app window my forrm closes with it. Is there a way I
> can
> get rid of this window and have only my form?
Sure, but you'll have to make a form class! ;-)
I usually do this: define the class I want to use as the form that
opens when my app is run, and then do:
app.MainFormClass = MyCoolFormClass
-- 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]
