Thanks greatly for the insight! Ironically, the main reason I was doing 
things this way was to get the constructor form and the Zinstances to *both 
work* and 'sing from the same method'. It was indeed the constructor form 
not working that was puzzling me. Oh well, back to the drawing board...

Just in case anyone has cracked the undelying issue: what I'd really like is 
some way to have both the ZClass constructor form and its ZInstances to use 
the same mechanism (encapsulated within the ZClass) for 'sourcing' selection 
list data. Just tell me it isn't possible and I'll move on...

Dieter Maurer <[EMAIL PROTECTED]> said:

> Bob Marshall wrote at 2003-7-18 09:04 -0000:
>  > ...
>  >   All the documentation I've read says that the 'selection' type for a 
>  > property of a ZClass property sheet can be a variable *or a method*. 
>  > This works as advertised, except where the method is a method *defined 
>  > within the Zclass* (e.g. as MyZClass.propertysheets.methods.myMethod ). 
>  > this a known bug? A feature? Do I need some arcane Zope Zen syntax to 
>  > this behaviour?
>  > 
>  >   N.B. If the method resides *outside* the ZClass (e.g. as a python 
>  > in the root folder) all things works just fine.
>  > 
>  >   The only 'diagnostic' I get is on the property sheet containing the 
>  > selection type property: it displays e.g. 'No value for myMethod' 
instead of 
>  > the expected drop-down box.
> I used this already and it worked (so I do not have time at the moment
> to check whether it still works).
> It will not work in the constructor form (as at that time there is
> not yet a ZInstance that can access "methods" directly).
> It should work as soon as you have a ZInstance.
> Dieter


Zope-Dev maillist  -  [EMAIL PROTECTED]
**  No cross posts or HTML encoding!  **
(Related lists - )

Reply via email to