Sign in to follow this  
QLNEO

Signal.addOnce arguments behaving funny

Recommended Posts

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

// Form 1
paddle.events.onDragStart.addOnce(ball.setMovement, ball);

// Form 2
paddle.events.onDragStart.addOnce(function() {
   this.setMovement();
}, 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

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.