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

Injector Warnings #25

Open
jonathantorres opened this issue Oct 11, 2011 · 4 comments
Open

Injector Warnings #25

jonathantorres opened this issue Oct 11, 2011 · 4 comments

Comments

@jonathantorres
Copy link

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.

@willdady
Copy link

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.

@dreammonkey
Copy link

hi,

I'm not sure if this thread is still active but I've been experiencing the exact same issue.
I'm using rl 1.5.2 in combination with signal command map and signal mediator. (both of which i believe to have the latest stable versions from git)

I'd like to add the following:
I believe the warning is printed only when dispatching the same signal multiple times in your code. i.e. in one of my most recent projects I started to see the warnings on a signal command that's responsable for navigational tasks (cfr. StateMachine).

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,
Diederik

PS: I love the rl framework in combination with signal commands, keep up the good work !

@weltraumpirat
Copy link

@webysther
Copy link

Me too.

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

No branches or pull requests

5 participants