I'm doing some tests here but apparently works.
Modifying the addBean method makes the command be instantiated when
the event gets called and handled on the CommandMap..
I'm not sure about the GC of the created command but the log messages
now makes more sense.
Take a look:
[SWF] SwizCommandBug.swf - 2,392,520 bytes after decompression
Swiz dispatcher set to SwizCommandBug0
Swiz domain set to null
Dispatched Swiz Created Event to find parent
Swiz domain set to [object ApplicationDomain]
Swiz global dispatcher set to SwizCommandBug0
Processors initialized
BeanFactory completing setup
BeanFactory::setUpBean( Bean{ source: [object ApplicationCommands],
name: null } )
BeanFactory::setUpBean( Bean{ source: [object ApplicationModel], name:
null } )
BeanFactory::setUpBean( Bean{ source: [object UserModel], name:
null } )
BeanFactory initialized
Set up event type set to addedToStage
Set up event phase set to capture phase
Set up event priority set to 50
Tear down event type set to removedFromStage
Tear down event phase set to capture phase
Tear down event priority set to 50
BeanFactory::setUpBean( Bean{ source: SwizCommandBug0, name: null } )
Swiz initialized
BeanFactory::setUpBean( Bean{ source: [object ExampleCommand], name:
null } )
InjectProcessor set up [Inject] on Bean{ source: [object
ExampleCommand], name: null }
InjectProcessor set up [Inject] on Bean{ source: [object
ExampleCommand], name: null }
executed
appModel: [object ApplicationModel]
userModel: [object UserModel]
I will probably fill in a new bug in Jira for this issue.
;)
On Apr 11, 5:18 pm, Brian Kotek <
brian...@gmail.com> wrote:
> I've never used the command map so I'm really not sure. If you change that
> in CommandMap, does it work correctly?
>
>
>
>
>
>
>
> On Mon, Apr 11, 2011 at 3:50 PM, William Lepinski <
wil...@gmail.com> wrote:
> > I guess I fix the bug changing the line 126 on
>
> >
https://github.com/swiz/swiz-framework/blob/master/src/org/swizframew...