Sign in to follow this  

Signal.addOnce arguments behaving funny

Recommended Posts

Please take a look at the two following pieces of code:

// Form 1, ball);

// Form 2 {
}, ball);

Technically these two should be the same. But, for some reason, the first variant isn't quite working according to the plan. In fact, ball is being sent as an argument to .setMovement() instead of being the context, as the docs make me think it should be. The second form works as expected, ball being treated as this.

Is this a bug, an example of badly explained documentation or I'm missing something obvious?

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.