Cursor is over object bug

  • Link to .capx file (required!):

    dropbox.com/s/qwklv57escj316f/Button%20Bug.capx

    Steps to reproduce:

    1. Start preview

    2. Hover your mouse over the buttons

    3. Move your mouse faster over the buttons then stop moving the mouse while keeping the cursor on the button

    Observed result:

    Some of the buttons will be in frame 1 even if they are not under the mouse cursor.

    Expected result:

    All buttons that are not under the cursor will set to frame 0. All that are should be in frame 1.

    Browsers affected:

    Chrome: yes

    Firefox: yes

    NW.js: yes

    Operating system & service pack:

    10,64

    Construct 2 version:

    Stable r259

  • Else will only run if the mouse isn’t over any buttons. If you move the mouse fast enough you can move it from one button to another without being on any resting space.

    Anyways it’s not a bug, but is an expected behavior when multiple instances are involved.

    There are a few ways you can do it differently so it does what you want. The first is to make a “for each button” event and put your two conditions as sub-events.

    Another idea is to just not use else and use an inverted “is over button” condition.

    Probably what I’d do is

    Every tick

    — button: set frame to 0

    Mouse is over button

    — button: set frame to 1

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • R0J0hound is correct. Closing as not a bug.

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