This is probably a easy one but.. i am confused all of a sudden about how I should handle this scenario.  I have a UserManager component that is similar to the EmployeeAdminDemo.  Basically the view component has a mode property that controls weather certain buttons, fields are displayed and enabled.  If a user is editing his own profile then certain controls like, userID, status and role should be disabled.  Also, if a user is an admin or super user then they will have access to certain controls that a regular user will not have.  Should I be managing this property and the responses to its changes using the custom event way or should I use the PureMVC communication system to send notifications to the view component's mediator?  Or does this even make a difference?

Thanks.

Hello,
I haven't delved much into the Pipes Utility for being afraid of being overwhelmed.  However, after a small refactor today, I think it may be time to make the plunge.  My application initially showed a data grid with summary data.  When the user clicked on an item the state would change sliding up the grid and showing a tab navigator with tabs showing the details of the selected grid item.  The change I made was to now show the details in a pop-up TitleWindow.  However, I now realize that I want to give the user the ability to work with more than one item at a time and still interact with the main application.  Would this be a scenario where the Pipes utility is relevant?

Thank you

Hi.  Is this an ok way to pass around data?

:

         
        //IN APPLICATION MEDIATOR
        // user was returned from the login proxy
        case LoginProxy.LOGIN_COMPLETE:
        // create a user instance from the body
        var user:UserVO = body as UserVO;
        // set the global application user
        appProxy.appUser = user;
        // the main screen view component has a label welcoming the user so I need to get the main screen mediator
        var mainScreenMediator:MainScreenMediator = facade.retrieveMediator( MainScreenMediator.NAME ) as MainScreenMediator;
        // main screen exposes a public variable called 'appUser' that is set by its mediator
        mainScreenMediator.setUser( user );
        // change the view to the main screen
        changeView( ApplicationFacade.MAIN_SCREEN );
        break;

Hello.  For some reason i am getting the Error: multitonKey for this Notifier not yet initialized!" error even though I only call the facade from the onRegister() function in the Mediators and from the execute() functions of the Commands.  I don't reference the facade at all in the onRegister functions of the proxies that I register on startup.  I am using the StartupCommand from an example I found that extends the MacroCommand.  All of this started happening after I tried to implement the StartupManager.  I wanted to pull some values from the database to populate a combo box that the user can set when logging in.  I didn't want the login view to be displayed if the combo box values are not populated.  I thought this thought the error was caused by making changes while going through the StartupManager getting started tutorial, but I changed everything back and I am still getting the error.  VERY FRUSTRATING!!  It absolutely worked before.  All of the posts I see on this topic say that it is because you have to get the facade.retrieve() from the onRegister() and I have done that.  Is there something else I am missing?  Thank you.

// Startup Command

:


public class StartupCommand extends MacroCommand
{
        override protected function initializeMacroCommand():void {
            addSubCommand( ModelPrepCommand );
            addSubCommand( ViewPrepCommand );
        }
}
// Model Prep Command

:

public class ModelPrepCommand extends SimpleCommand
{
override public function execute(note:INotification):void
{
facade.registerProxy( new ApplicationProxy() );
facade.registerProxy( new UserProxy() );
facade.registerProxy( new LoginProxy() );
facade.registerProxy( new RegistrationProxy() );
}
}
// View Prep Command

:

override public function execute( note:INotification ):void
{
var app:MYMVCAPP = note.getBody() as MYMVCAPP;
facade.registerMediator( new ApplicationMediator( app ));
}