16 Jul 01:13
Re: probable bug in @on_trait_change with delegated lists
From: David C. Morrill <dmorrill@...>
Subject: Re: probable bug in @on_trait_change with delegated lists
Newsgroups: gmane.comp.python.enthought.devel
Date: 2008-07-15 23:13:51 GMT
Subject: Re: probable bug in @on_trait_change with delegated lists
Newsgroups: gmane.comp.python.enthought.devel
Date: 2008-07-15 23:13:51 GMT
Danny Shevitz wrote:
>> I'm not sure why you think that is the wrong handler, especially when
>> the 'new' value is a TraitListObject? If 'new' were a TraitListEvent
>> object, then your conjecture would have some merit. See my previous post
>> about setting a default Property value...
>>
>> Dave Morrill
>>
>>
>
> my bad, new *is* a TraitListEvent, not a TraitListObject as written, so I
> believe my comment has merit.
>
> As for sub_contexts, it is defined via
>
> class ExtendableGate(HasStrictTraits):
> sub_contexts = List
>
> class ExtendableContext(HasStrictTraits):
> logic_element= Instance('ExtendableGate')
> sub_contexts = Delegate('logic_element', modify=True)
>
>
Hmm...might bear some looking into. I'm still not clear what is
happening in your app when the notification error occurs. Which trait is
being modified, and how? I probably won't have time to look into it
today, but will try and do so tomorrow...
Dave Morrill
RSS Feed