Webclient: flick() never ends or just sets the input state as the icon_state.

ID:1856412
 
May 21 2015, 10:41 pm
Resolved
flick() did not end properly until the atom moved.
BYOND Version:507.1285
Operating System:Windows 7 Ultimate 64-bit
Web Browser:Chrome 42.0.2311.152
Applies to:Webclient
Status: Resolved (508.1289)
This issue has been resolved.
Descriptive Problem Summary:

As the title suggests, in the latest byond build there is an issue with the flick() function repeating the icon state animation until the atom that the flick is applied to has changed location (either through a Move() call or not).

This behaves identically to just setting the icon_state of an atom to whatever you're trying to flick.
May 22 2015, 9:43 am (Edited on May 22 2015, 12:46 pm)
Is this 507.1284? I fixed some bugs specifically with animation and flicks in that version.
May 22 2015, 12:25 pm
In response to Lummox JR
I was wondering if this existed since I use flick() a bit (but never noticed an issue), so I tested it myself. I didn't experience a problem in either 507.1284 or 507.1285.

player
    parent_type = /combatant

    Login()
        ..()
        flick("run", src)
May 22 2015, 3:48 pm
I tested this on 507.1285 and I am experiencing the issue exclusively on the webclient.
May 22 2015, 4:07 pm
Okay, thanks. I edited your report to include the full version number.
Jun 9 2015, 7:50 pm
Can confirm this is still an issue in 508.1287.
Jun 10 2015, 4:52 pm
Lummox JR resolved issue with message:
flick() did not end properly until the atom moved.
Jun 10 2015, 5:25 pm
In response to Lummox JR
YES!
Jul 31 2015, 5:36 pm
Experiencing this in 508.1288 in the webclient still. I'm also experiencing abnormal world CPU when virtually nothing is going on. Confirmed both in a basic test project and can send if necessary.

Edit: DS has no problems.
Jul 31 2015, 10:40 pm
508.1288 isn't current. Multiple fixes to the webclient were done in subsequent versions. But that's probably moot with DSificaiton. The CPU usage you're seeing is definitely a result of the old webclient and the DSified version will be much better on that as well.
Jul 31 2015, 11:16 pm
In response to Lummox JR
My fault, I meant 508.1292.

I just tested in the latest beta and the flick() issue is indeed fixed. Nothing to see here I suppose. (Looking forward to the DSified webclient.)