Function bug

  • Problem Description

    Bug on function call

    Attach a Capx

    http://www.filedropper.com/bug_1 (on page press "Download this file")

    http://www.filedropper.com/bug2 (on page press "Download this file")

    Steps to Reproduce Bug

    Execute capx

    Observed Result

    Error message

    Affected Browsers

    • Chrome: YES
    • FireFox: not tested
    • Internet Explorer: not tested

    Operating System and Service Pack

    Win 8.1 64-bit

    Construct 2 Version ID

    233 64-bit

  • 1. That's a terrible file-sharing site.... just FYI.

    2. You have not found a bug... You are not using the keyboard or function.call methods correctly.

    See the manual pages that refer to these events and, if you're still stuck, I suggest you post a question in the "How do I" forum.

  • Colludium, try out this capx http://www.filedropper.com/bug2. Is this not a bug too?

  • Are you purposely not passing in the name, or are you missing the point that you aren't specifying the function name at all. It's not clear. You should be calling this:

    Function.Call("Function",Variable1)

  • Are you purposely not passing in the name, or are you missing the point that you aren't specifying the function name at all. It's not clear. You should be calling this:

    Function.Call("Function",Variable1)

    Oh yeah, that works. Thank you!

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • Yeah the real problem is you're circumventing the type check using a global variable to pass a number where you should pass a string.

    Ideally C2 would reject this as an invalid expression but then changing the type of global variables could invalidate large numbers of expressions. That's not such a nice consequence. So closing as won't fix.

  • Yeah the real problem is you're circumventing the type check using a global variable to pass a number where you should pass a string.

    Ideally C2 would reject this as an invalid expression but then changing the type of global variables could invalidate large numbers of expressions. That's not such a nice consequence. So closing as won't fix.

    Thank you, Ashley!

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)