Comments on: Handling Popup Logic in PureMVC *Update* http://www.newtriks.com/?p=329 Flex, Flash & AIR Development Sun, 05 Sep 2010 01:10:47 +0000 hourly 1 By: Dave http://www.newtriks.com/?p=329&cpage=1#comment-31464 Dave Thu, 27 May 2010 15:53:18 +0000 http://www.newtriks.com/?p=329#comment-31464 Hi Simon, Just tried implementing your code but keep getting this error: "TypeError: Error #1009: Cannot access a property or method of a null object reference." At the line: "PopManager.openPopUpWindow( ApplicationFacade.getInstance( this.multitonKey ), CustomPop, CustomPopMediator, true, 0, 0, "custom_pop", true );" In the PopManager class. Obviously I've modified this all to fit in with my existing app. It would appear that the something hasn't finished being initiated before it's being called. But, I've tried tracing it all out and can't spot anything wrong. Any ideas? Has the PureMVC swc been updated since this demo? Thanks! Hi Simon,
Just tried implementing your code but keep getting this error:
“TypeError: Error #1009: Cannot access a property or method of a null object reference.”
At the line:
“PopManager.openPopUpWindow( ApplicationFacade.getInstance( this.multitonKey ),
CustomPop,
CustomPopMediator,
true,
0, 0,
“custom_pop”,
true );”
In the PopManager class.
Obviously I’ve modified this all to fit in with my existing app.
It would appear that the something hasn’t finished being initiated before it’s being called. But, I’ve tried tracing it all out and can’t spot anything wrong.
Any ideas? Has the PureMVC swc been updated since this demo?
Thanks!

]]> By: AJ Simon http://www.newtriks.com/?p=329&cpage=1#comment-31026 AJ Simon Wed, 07 Apr 2010 17:17:53 +0000 http://www.newtriks.com/?p=329#comment-31026 i had to make a few adjustments to this but.... this worked like a charm and saved me a ton of time! i had to make a few adjustments to this but…. this worked like a charm and saved me a ton of time!

]]> By: Tweets that mention Handling Popup Logic in PureMVC *Update* -- Topsy.com http://www.newtriks.com/?p=329&cpage=1#comment-31025 Tweets that mention Handling Popup Logic in PureMVC *Update* -- Topsy.com Wed, 07 Apr 2010 13:30:26 +0000 http://www.newtriks.com/?p=329#comment-31025 [...] This post was mentioned on Twitter by Dennis Plucinik. Dennis Plucinik said: Reading: Handling Popup Logic in PureMVC *Update*: http://bit.ly/bdYLos [...] [...] This post was mentioned on Twitter by Dennis Plucinik. Dennis Plucinik said: Reading: Handling Popup Logic in PureMVC *Update*: http://bit.ly/bdYLos [...]

]]> By: Jason http://www.newtriks.com/?p=329&cpage=1#comment-30624 Jason Thu, 17 Sep 2009 19:24:07 +0000 http://www.newtriks.com/?p=329#comment-30624 Ok, got it thanks. So, if I want the popup to appear at the top and direct center (horiz) of a certain component on stage, how would I go about doing that. So I click a component on screen, say a sprite, I want my popup to appear 10 pixels above the component I clicked and centered horiz over the clicked component? Any suggestions? Ok, got it thanks.

So, if I want the popup to appear at the top and direct center (horiz) of a certain component on stage, how would I go about doing that.

So I click a component on screen, say a sprite, I want my popup to appear 10 pixels above the component I clicked and centered horiz over the clicked component?

Any suggestions?

]]> By: newtriks http://www.newtriks.com/?p=329&cpage=1#comment-30615 newtriks Fri, 11 Sep 2009 18:10:57 +0000 http://www.newtriks.com/?p=329#comment-30615 So you want to load a popup on application creation complete, do you mean without any user interaction? It depends on your setup a suggestion would be to use your startup command to fire off the HANDLE_POP notification, or onRegister() in your ApplicationMediator, etc..... Is this what you mean? So you want to load a popup on application creation complete, do you mean without any user interaction? It depends on your setup a suggestion would be to use your startup command to fire off the HANDLE_POP notification, or onRegister() in your ApplicationMediator, etc….. Is this what you mean?

]]> By: Jason http://www.newtriks.com/?p=329&cpage=1#comment-30614 Jason Fri, 11 Sep 2009 17:53:53 +0000 http://www.newtriks.com/?p=329#comment-30614 So when I use these classes and I have my popup dispatching and event the mediator doesn't hear the event. If I attach an eventlistener on the main stage to listen for the events from the popup the stage hears the events. Here is how I instantiate the popup from the stage. var pObj:PopDataVO = new PopDataVO(); pObj.type = ChooseViewIntroPanel.CHOOSE_VIEW_INTRO_PANEL; facade.sendNotification( ApplicationFacade.HANDLE_POP, pObj, ResourceConstants.OPEN_POP ); You might say you shouldn't do that from the stage, but rather from a command or another mediator like the stageMediator. The issue is this popup is the firs thing that happens when the app loads. Think of a popup you get in dreamweaver or photoshop. J So when I use these classes and I have my popup dispatching and event the mediator doesn’t hear the event. If I attach an eventlistener on the main stage to listen for the events from the popup the stage hears the events.

Here is how I instantiate the popup from the stage.

var pObj:PopDataVO = new PopDataVO();
pObj.type = ChooseViewIntroPanel.CHOOSE_VIEW_INTRO_PANEL;

facade.sendNotification( ApplicationFacade.HANDLE_POP, pObj, ResourceConstants.OPEN_POP );

You might say you shouldn’t do that from the stage, but rather from a command or another mediator like the stageMediator.

The issue is this popup is the firs thing that happens when the app loads. Think of a popup you get in dreamweaver or photoshop.

J

]]> By: yeremy http://www.newtriks.com/?p=329&cpage=1#comment-30582 yeremy Mon, 03 Aug 2009 16:25:19 +0000 http://www.newtriks.com/?p=329#comment-30582 Thanks! :) Thanks! :)

]]> By: newtriks http://www.newtriks.com/?p=329&cpage=1#comment-30578 newtriks Wed, 22 Jul 2009 13:19:23 +0000 http://www.newtriks.com/?p=329#comment-30578 well have one view component with 2 viewStates and when you inject the data pass a param to define the state to show, easy ;) well have one view component with 2 viewStates and when you inject the data pass a param to define the state to show, easy ;)

]]> By: Claudiu http://www.newtriks.com/?p=329&cpage=1#comment-30577 Claudiu Wed, 22 Jul 2009 12:51:33 +0000 http://www.newtriks.com/?p=329#comment-30577 Ok so if I have a message pop-up and a login pop-up I want both of them to be handled by the same mediator instead of writing 2 mediators since i can extend the case from command. I just want to use this for showing and hiding them ... Each op-ups will have the business logic handled outside this ... wel maybe the message will be injected with data when called but aside from that i don't see why register 2 mediators when I can show and hide different pop-ups with just one... If I had 2 mediators, the only place where one will be different from the other will be the getter that casts to the to the actual view component and the component class ref ... Am I making sense here? C Ok so if I have a message pop-up and a login pop-up I want both of them to be handled by the same mediator instead of writing 2 mediators since i can extend the case from command. I just want to use this for showing and hiding them … Each op-ups will have the business logic handled outside this … wel maybe the message will be injected with data when called but aside from that i don’t see why register 2 mediators when I can show and hide different pop-ups with just one… If I had 2 mediators, the only place where one will be different from the other will be the getter that casts to the to the actual view component and the component class ref … Am I making sense here?

C

]]> By: newtriks http://www.newtriks.com/?p=329&cpage=1#comment-30576 newtriks Wed, 22 Jul 2009 12:37:13 +0000 http://www.newtriks.com/?p=329#comment-30576 Currently the only potential repetition is the code in the switch statement i.e. for checking if the popup mediator is registered and then calling the PopManager.openPopUpWindow() method which is minor. That complete means you now have the popup either registered or unregistered with the facade. The final code snippets at the end of my post show how to open and close a popup and you would only need to change the body() attribute of the notification for each popup you want to open/close. So unless I am completely misunderstanding you there should be minimal duplicate code. Currently the only potential repetition is the code in the switch statement i.e. for checking if the popup mediator is registered and then calling the PopManager.openPopUpWindow() method which is minor. That complete means you now have the popup either registered or unregistered with the facade. The final code snippets at the end of my post show how to open and close a popup and you would only need to change the body() attribute of the notification for each popup you want to open/close. So unless I am completely misunderstanding you there should be minimal duplicate code.

]]>