I think I may need to follow your suggestion - when I changed from dDialog
to dForm I got an error wuth the modal = true staement. After I removed that
the dialog just flashed up on the screen and disappeared before I could
click the button.
Not sure what you mean by saving the attribute reference and then
referencing it. The dDialog has no such attribute ...
Rodgy
----- Original Message -----
From: "Paul McNett" <[email protected]>
To: "Dabo Users list" <[email protected]>
Sent: Tuesday, December 16, 2008 1:12 PM
Subject: Re: [dabo-users] Fw: Fw: Running a Report
> Ed Leafe wrote:
>> On Dec 15, 2008, at 7:33 PM, Roger Lovelock wrote:
>>
>>> I suspect that this is because FrmReportBase.py inherits from
>>> dDialog rather
>>> than a form type and therefore a bizObj can't be added. If so, I
>>> guess I
>>> will need to convert FrmReportBase to a form rather than a dialog.
>>> Am I right?
>>
>>
>> Correct. We originally designed dForm to contain the bizobj logic,
>> assuming that we would be able to use it modally or non-modally as
>> needed, but for some reason that ability never got added to wxPython.
>> The idea was that dDialog would be for dialogs, which are always
>> modal, and dForm would be the general-purpose main container.
>
> Roger,
>
> You can either change to use a Form like you suggested, or if you need
> true modality,
> keep using the dialog and save the attribute reference to the dialog, such
> as:
>
> def initProperties(self):
> self.mybiz = biz.Clients(...)
>
> and then when you need it:
>
> def onHit_blah(self, evt):
> self.mybiz.requery()
>
> Paul
>
>
[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/4b817cc574a94f7396c36539a312b...@roger
