-
Notifications
You must be signed in to change notification settings - Fork 43
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
Injector Warnings #25
Comments
I too am having the same issue under Robotlegs 1.5.2. I am getting the warning when dispatching a signal from a command where the signal is mapped to a command in my context. |
hi, I'm not sure if this thread is still active but I've been experiencing the exact same issue. I'd like to add the following: In an other project I got the warning on a signal command that got dispatched from a service that received frequent update events from a wowza server. I am not yet certain if this behavior breaks the code / logic / mapping in anyway. I am however concerned if the warning has influence on the performance of the production swf... Would it be advisable not to use signal commands for broadcasts that occur frequently? Kind Regards, PS: I love the rl framework in combination with signal commands, keep up the good work ! |
The same issue and a possible solution can be found here: http://stackoverflow.com/questions/12759831/robotlegs-warning-injector-already-has-a-rule-for-type/12767463#12767463 |
Me too. |
Hi, I just updated my current project from RL 1.4 to 1.5.1 and everything seems fine, except that I get this warning everytime that I dispatch a new Signal. The Signal carries a Sprite and a String reference.
Warning: Injector already has a rule for type "flash.display::Sprite", named "".
If you have overwritten this mapping intentionally you can use "injector.unmap()" prior to your replacement mapping in order to avoid seeing this message.
Warning: Injector already has a rule for type "String", named "".
If you have overwritten this mapping intentionally you can use "injector.unmap()" prior to your replacement mapping in order to avoid seeing this message.
Am I doing something wrong? I don't understand what the warning means.
The text was updated successfully, but these errors were encountered: