The forum on this site is closed for new comments and posts. Continue the conversation in the new forum, and learn more here.

How can I manually disable tap functionality from a script?

  • Hey Scott! If you are using the Behavior System to trigger the throw (e.g. triggering a Tween), you can use the "Set Interval" feature to disable the trigger from happening again over a tunable number of seconds. Check it out here:

    https://lensstudio.snapchat.com/guides/scripting/behavior-script/

    If you're scripting on your own, the best way is to have a bool (e.g. called throwing) that blocks the throw when it's true. Then, you set it to true when the throw happens. You can then set it back to false after some amount of time using a DelayedCallbackEvent. 

    https://lensstudio.snapchat.com/api/classes/DelayedCallbackEvent/

    Comment actions Permalink
  • Thank you! Though the delayedcallbackevent doesn't seem to be triggering at all in my script. Mind taking a look at my snippet below? I never make it to print("RESET");

     

    function onTap(eventData) {
     print("Snowball Tapped");
     var arrowPosition=script.arrow.bindingPoint;
     var newX=arrowPosition.x*1500;
     print("arrow X value: "+newX);
     var throwDirection=newvec3(newX, 650, -650);
     global.tweenManager.setEndValue(script.snowball, "snowball_move",   throwDirection);
     global.tweenManager.startTween(script.snowball, "snowball_move",   moveComplete,  moveStart);
     
     var handleCollision=script.createEvent("DelayedCallbackEvent");
     handleCollision.reset(2);

     handleCollision.bind(function (eventData) {
      global.tweenManager.resetObject(script.snowball, "snowball_move");
      print("RESET!");
     });
    }
    var tapEvent = script.createEvent("TapEvent");
    tapEvent.bind(onTap);
    Comment actions Permalink
  • also my tweenManager.resetObject doesn't seem to be working at all.....? Even outside of the delayedcallback

    Comment actions Permalink
  • Hi Scott,

    I tried running your code in a small test project, and it all seems to work correctly for me: "RESET!" is being printed out.

    Is it possible that something's going wrong in your "moveComplete" or "moveStart" functions? Maybe this object is being disabled? That's my best guess for why we're seeing different results.

    For resetObject(), it should work correctly if you stop the tween first before resetting it. So you can add this line before calling resetObject:

    global.tweenManager.stopTween(script.snowball, "snowball_move");
     
     

     

    Comment actions Permalink

We're here to help! We just need a little bit of information...

What system are you using?

Have you downloaded the latest version of Lens Studio?

Please download the latest version of Lens Studio. If you still run into this issue, please come back and report it!

Is this issue causing Lens Studio to crash?

What system do you run Lens Studio on?

Version

Graphics

Follow the next steps to help us solve your issue:

  • Copy and paste this text into your TerminalCommand Window
    open ~/Library/Preferences/Snap/Lens\ Studio/ %LOCALAPPDATA%\Snap\Lens Studio Copy Text
  • Press ReturnEnter to run the command. The Lens Studio folder will automatically open
  • Prepare to upload your files: zip the "Log" Folder by right-clicking and choosing "compress."
    Locate the Log.txt file right above it.

    Attach a screenshot of the issue:

Name:

Email:

What is this most relevant to?

Please enter a brief description of your issue:

Thanks for submitting this issue.

Unfortunately, it's likely due to the operating system or hardware you're using – since they don't meet the system requirements for Lens Studio.

Still, we hear you loud and clear, and are logging the issue in case there's ever a workaround we can provide!

Minimum Requirements

Operating System: Windows 10 (64 bit); MacOS 10.11+

Hardware: Minimum of Intel Core i3 2.5Ghz or AMD Phenom II 2.6Ghz with 4 GB RAM; Intel HD Graphics 4000 / Nvidia GeForce 710 / AMD Radeon HD 6450 or better; screen resolution of 1280x768 or higher

We'll try to resolve this issue as soon as possible. Thanks for letting us know about it!

Keep an eye out for a followup email from us. We may have a couple more questions for you, or we might already have a solution to offer.

Happy creating!