[r180] UI elements bug/inconvenience

0 favourites
  • 2 posts
From the Asset Store
Various, high-quality, multiple resolution elements for castles.
  • Problem Description

    Not really sure if this is even a bug as much as an inconveniency. But if you create a sliderbar or any other system UI element such as buttons etc. And press "tab" until it is selected/highlighted. There are no way to deselect it again unless you press "Tab" once more.

    For the buttons you can use unfocus, but something like this doesn't exist for the sliderbar, and not sure there is a good way to deal with it for buttons anyway.

    The problem is that keyboard input doesn't work while one of these are selected.

    Maybe an option to remove these elements from working with "Tab" or something. Anyway not the biggest problem ever just inconvenient if you use them.

    Attach a Capx

    Not capx related

    Description of Capx

    Steps to Reproduce Bug

      Create any system UI element and tab during runtime until it is selected. Make something that react to a "key press" and it wont work, while the element is selected.

    Observed Result

    While selected keyboard input doesn't work.

    Expected Result

    Affected Browsers

      Tested with Node webkit

    Operating System and Service Pack

    Windows 7

    Construct 2 Version ID

    r180 but most likely all versions as these are system elements.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • I think this should be fixed in the next build, since it unfocuses form controls when you click away from them.

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