createObj fires token:change?

Hi, I was under the impression that things done by the API shouldn't fire change events. I've just spent a while debugging a weird issue in one of my scripts, and I finally realised that a call to createObj was resulting in a (apparently synchronous) firing of a "token:change" event. Is this intended behaviour or is it a bug? I've never noticed this behaviour before, so I wonder if there's some sort of regression? Lucian

I think it's always done it. I have done thing like this... if ( 'add' === obj.get('controlledby') ) { obj.set('controlledby', ''); return; } ...to get around it. Better ways to deal with it I am sure.