On Thu, Jun 17, 2010 at 11:35 PM, Rajarshi Guha <rajarshi.guha@...> wrote:
> On Thu, Jun 17, 2010 at 5:14 PM, Egon Willighagen
> <egon.willighagen@...> wrote:
>> On Thu, Jun 17, 2010 at 11:13 PM, Rajarshi Guha <rajarshi.guha@...> wrote:
>>> I think that a change even should be fired on when the property actually changes
>> You mean "even when it does not actually change"?
> Umm, no? if the property changes in value, then the change event
> should be fired.
Ah... you wrote "a change evenT"... instead of "a change, even ..." ! :)
> The current behavior essentially says that 'a property has been set'
OK, so you 'oppose' Gilleain's idea then, that events should always be
thrown at 'set'... ?
I'm actually fine with both... it's just where you put the effort...
CDK community, more input please!
Post-doc @ Uppsala University
Proteochemometrics / Bioclipse Group of Prof. Jarl Wikberg