Function call not executing.

0 favourites
  • 5 posts
From the Asset Store
Basic clone of a 80's arcade game called Gyruss that was quite fun to play!
  • I followed this BUG report.

    Now, i am not supposed to write in a closed bug report. But i found this one very intriguing.

    I understand why it is closed. Lots of events, and they are a bit done in a way that i would not do. Yet, they are very simple.

    Nothing new, just functions calling functions. No reason to (almost every one in here is smarter then i am) run away from it on first glance.

    I added logging with the browser plugin. You can find them easy with the search function. Reducing everything to a few events.

    I added a 'alien' function call.

    Follow the instructions as given by the OPP in the other topic.

    Bring up the console in the browser.

    You can clearly see that there is a log entry before calling the function, but no log entry from within the function.

    Conclusion, the function is not called (the first time).

    Why?

    Would appreciate if you look into this. Because i dont understand it, and it makes me distrust functions.

    Thanks.

  • I too am curious. HOWEVER: I looked at the capx - although it's all basic stuff it is also a horrendous and thinly-commented mess. I can't help but imagine whoever kept this project is very capable of making mistakes, and in code that messy they are easily hidden.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • There are mistakes in there. Yet, it comes to that point that the function is called. Browser log actions right before that function call do log in the console, but the function is not called.

  • There are two places that function is called

    Events 329 to 332 for the first screw

    and events 318 to 321 for the following screws.

    It can be obseved that no function call works in events 329 to 332. Explination? The function object isn't picked, and the cause is the "or" event on line 323.

    Comment and link to new bug:

  • Thank you Sir for figuring that out and for the following up BUG report.

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