Hi Ben, You really don't want to control the Cairngorm views directly, in a command. This defeats encapsulation. You would usually change controls in a view: through binding to a ModelLocator variable, using the Observe tag or (if you're desperate) dispatching an event (from the command) that is listened for by the view. The first two are recommended by the Cairngorm gurus.
-TH __________________________________ Tim Hoff Cynergy Systems, Inc. http://www.cynergysystems.com Office <http://www.cynergysystems.comoffice/> : 866-CYNERGY --- In [email protected], "ben.clinkinbeard" <[EMAIL PROTECTED]> wrote: > > Hello, I have a command that gets called from a few different views, > and when it returns (it makes a WS call), it needs to update a control > in the view that initiated the call. The approach I am considering is > to pass the view reference in the event that is dispatched (its > already a subclass of CairngormEvent with its own properties) and then > calling a function on that event param in my command's result handler. > Something like this: > > cancelEvent.callingView.doStuff(); > > Is there any reason I should avoid this or perhaps a better way? I am > thinking that a better (more decoupled) way might be to pass the view > and function name, and then call the function via apply. Something > like this: > Function(cancelEvent.callingView["funcName"]).apply(cancelEvent.callingV\ iew); > > Thoughts? Suggestions? > > TIA, > Ben >
