On 2004-03-02 2:15 PM, Ian Beatty is reputed to have said:

> Here's what I have now: a hierarchy of five custom
> classes, pretty close to identical for now. All five subclass ObjectManager,
> CatalogAware, PropertyManager, and SimpleItem in that order. The top one
> ("A") may be added to any old Zope folder; B may only be added to A; C to B;
> D to C; and E to D. Standard Zope Images may be added to E.
> 
> I can now freely rename A, C, D, and any images within an instance of E. I
> *cannot* rename B or E; when I try, I get "The object term_0 does not
> support this operation" ('term_0' is an instance of B)

On 2004-03-02 9:55 AM, Chris Withers is reputed to have said:

> I suspect the way you're trying to ensure only certain types of object can go
> in certain containers is to blame here...

Aah, finally, I figured it out. So simple. You were right, Chris.

For the problem classes, B and E, the meta_type value defined in the class
definition wasn't exactly the same as the type name specified in the
container class' all_meta_types' field.

*Sigh* And I thought that value in all_meta_types was simply to provide the
visual label in the combo box.

Thanks for the help, folks. I definitely needed it.

Cheers,

..Ian

-- --- -- --- -- --- -- --- -- --- -- --- -- --- -- --- -- --- --
Dr. Ian Beatty                           [EMAIL PROTECTED]
Physics Education Research Group              voice: 413.545.9483
Department of Physics                           fax: 413.545.4884
Univ. of Massachusetts              AIM: (available upon request)
Amherst, MA 01003-4525 USA       http://umperg.physics.umass.edu/
-- --- -- --- -- --- -- --- -- --- -- --- -- --- -- --- -- --- --



_______________________________________________
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to