Number one sort of breaks my hope for encapsulation but 2 works like a charm. Thanks Bhuvan.
-Kenny --- In [email protected], Bhuvan Gupta <[EMAIL PROTECTED]> wrote: > > 1. Can't you access the model directly inside the GetUsersCommand to > get the role value ? > > or > > 2. when you assign the nextEvent to GetUsersCommand inside > AddUserCommand set the nextEvent.data to role value. > > IMO, the above should work. > > On Feb 21, 2007, at 7:53 PM, lostinrecursion wrote: > > > Hi all, > > > > Forgive me if this is simple but I just can't seem to make it work. I > > have a command that fires each time a new record is added via > > SequenceCommand. (So, for example, AddUserCommand fires > > GetUsersCommand in the executeNextCommand function) > > > > The problem is that my GetUsersCommand is role based expecting a > > numeric role value from my model object and returning records only > > available to that particular user type. > > > > However, when I go ahead and try to add the "role" property to my > > nextEvent variable within AddUserCommand, the compiler throws a > > "possibly undefined property" error. > > > > How can I attach properties to events in my SequenceCommands then? > > > > -Kenny > > LIR > > > > > > >
