Text falls from text box while scrolling to a moving object

0 favourites
  • 3 posts
From the Asset Store
This is a single chapter from the "Construct Starter Kit Collection". It is the Student Workbook for its Workshop.
  • Problem Description

    Text falls from text box while scrolling to a moving object.

    Attach a Capx

    1drv.ms/1Nx3bKO

    Description of Capx

    There is a text box with text in it and a sprite with Scroll To and Path Finding behaviors. When you press space, the object will move along the path it found at the start of the layout. Then the text in the text box will chang its place.

    Steps to Reproduce Bug

    • Make a layout with width = 1000
    • Make the window width = 500 (half layout width)
    • Add a text box in the left side of the layout. Fill it with any text.
    • Add an object with enabled Scroll To and Path Finding behaviors.
    • At the start of the layout, make the object find a path to the center of the right side of the layout.
    • Add Keyboard or mouse objects, and when the player presses a button (space or left-mouse) the object moves along its path.

    Observed Result

    In Chrome: The text leaves the text box and moves down then back up again.

    In Chrome, FF and IE: the text is pushed by the edge of the window to the right side of the text box.

    Expected Result

    The text should stay inside the text box and stay aligned to the left.

    Affected Browsers

    • Chrome: (YES)
    • FireFox: (YES)
    • Internet Explorer: (YES)

    Operating System and Service Pack

    Windows 8 Pro 64-bit

    Construct 2 Version ID

    200 built at 14:47:58 on March 16 2015

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Hi,

    Why don't you use a text object ? (instead of textbox object)

  • I can't reproduce in IE or Firefox, although your bug report seems to indicate they are affected. Also Chrome Canary is not affected, so this appears to be a Chrome browser bug that has already been fixed. We had a similar bug report with exactly the same conclusion recently so I think this is in fact the same issue. It should be fixed when Canary makes its way down to the stable channel.

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