Hey Tammo, I'm a bit ambivalent about that modification. It would certainly be useful but so far we've avoided "leaking" the OModel to a public interface. We really want to be able to change the OModel at will without worrying about APIs migration. And passing the variable gives you access to a lot of internal objects.
Isn't there any other way for you? Cheers, Matthieu On Nov 28, 2007 5:55 AM, Tammo van Lessen <[EMAIL PROTECTED]> wrote: > Hi guys, > > do you have objections to including the OScope.Variable in > VariableEvents instead of only the name? This is very useful when > working with extension attributes on variable declarations. I know this > is quite a corner case but makes the eventlistener API more powerful > (aside from the fact that I need it in my project ;) ) > > The same actually applies for activity events... > > Best, > Tammo >
