On Tuesday 30 September 2008 05:37:26 pm Dave Rowe wrote:
> On Tue, 30 Sep 2008 19:33:35 -0500, Ed Leafe <[EMAIL PROTECTED]> wrote:
> > Ah, my mistake. The Wizard form is based on the dialog class, not the
> > form class.
> >
> > If you don't need the wizard to be run modally, you can use a
> > dPageFrameNoTabs to create wizard-like behavior in a normal form.
> >
> > -- Ed Leafe
>
> So, is there not a way to tie the inputs on the WizardPage to the BizObj,
> such that it binds, and saves a new record upon clicking 'Next' or
> 'Finish'? Would the best practice (if still using the Wizard) to manually
> build the INSERT statement? I'm not opposed to it, necessarily, just want
> to make sure I'm not violating a design rule in Dabo or something :)
>
> Thanks,
> Dave
You could subclass the dialog and pass 'self' to the subclassed dialog. Don't
forget to call the super(). Since you passed the form (self) you can use it
within the Class.
callingForm.PrimaryBizObj.new()
callingForm.PrimaryBizObj.setFieldVal('fieldName', value)
callingForm.save()
That said, I think you are best served by not using a dialog but a form. What
I understood you want to call the wizard when the user opens the app for the
first time. I'd have code that checked the user preferrence DB for a flag or
some field. If the flag/field was "this is the first time" I'd call my form.
Check out "dUserSettingProvider.py" for how to use the settings.
--
John Fabiani
_______________________________________________
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]
