Ed Leafe wrote:
> On Jun 5, 2007, at 10:48 AM, Dabo Demo wrote:
>
>>> Did this change too.
>>> Now there is still no Connection.
>>> I didn't understand what Ed said about CxnFile, CxnName.
>>> Should i get a connection with this?
>> Why does CxnFile, CxnName work in CD but not in code?
>>
>> Should i set the Connection myself in initProperties of my Form?
>>
>> Please help as i do not understand the differences between CD and
>> code.
>
> Moving this off of Trac, since it's really annoying to me to have to
> converse in that format.
>
> The two properties 'CxnFile' and 'CxnName' were added to the Class
> Designer in order to permit it to store that information. Previously,
> it was always handled in code using:
>
> self.Application.addConnectFile("my.cnxml")
> cxn = self.Application.getConnectionByName("theConnection")
>
> When the QuickLayoutWizard was added a few months ago, these props
> were added to the Class Designer in order to persist the values
> selected. The main form class was modified to intercept these props
> if they were passed, and use them to perform the code I included
> above with the passed values.
>
> I have no problem with moving these props to the dForm level. Paul,
> do you see any potential problems with doing this?
>
Are you saying, that if you would have integrated them as python
properties, it should get handled in dFormMixin the same way as it works
in CD forms?
For what is that code in dFormMixin.__init__() (check of CxnFile,
CxnName) good for? Is it for nonstandard usage of the framework?
I still don't understand why CD forms get different handling than coded
forms.
Uwe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message: http://leafe.com/archives/byMID/dabo-dev/[EMAIL PROTECTED]
