Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EventGenerator sequence is null when set in a separate MXML component #13

Open
GoogleCodeExporter opened this issue Apr 23, 2016 · 1 comment

Comments

@GoogleCodeExporter
Copy link

Thank you very much for your framework. Great work guys!

Here is the issue I faced that might not be related to
an actual framework issue but perhaps a misunderstanding.

1. I create a separate MXML component holding Eventgenerator declaration 
(in attached)
2. I reference the component in the main application view
3. I start the sequence in calling the dispatch method on the referenced 
component

The sequence of events shall be dispatched.
Instead, I get a "Cannot access a property of a null object reference".
I attach the debug screen of FB that points the location of the issue.

Latest source version is used.
When the same code in the external MXML component is put in the
main application MXML the sequence is working.

I'm looking forward to any answer. Thanks.
Cédric

Original issue reported on code.google.com by rackamth...@yahoo.com on 5 Nov 2008 at 9:02

Attachments:

@GoogleCodeExporter
Copy link
Author

Hello,

I found my issue, I had to nest EventGenerator in a UIComponent
in order for home to dispatch event... As explained in the
Thomas PDF Documentation.


Cédric

Original comment by rackamth...@yahoo.com on 6 Nov 2008 at 3:36

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant