ID:1809109
 
Resolved
flick() did not work correctly on atoms with pixel movement.
BYOND Version:507
Operating System:Windows 7 Pro 64-bit
Web Browser:Chrome 41.0.2272.89
Applies to:Webclient
Status: Resolved (507.1276)

This issue has been resolved.
Descriptive Problem Summary:

On BYOND 507.1275 it seems that calling flick() or modifying any icon properties (most noticeably pixel x/y) of an item when it is not moving will not properly update it on the actual map display. A picture is worth a thousand words, and a gif is worth whoa maybe billions:

[Gif]

The projectile is actually moving via pixel projection, but instead, the pixel x/y values are only updated when the projection code actually modified the projectile's location. An atom will not display its flick() animation unless the atom's location changes, as well.

I'll admit it's kind of hard to see in that gif, but that's the best example I can show.
Did you download the new 1275? I know we had made a test build for WANO to try but there was a fix to the flick() issue. I fixed something related to pixel offsets earlier today that will be taken care of in 1276. I'll recheck flick() just to be safe.

[edit]
I'm definitely not seeing a problem with flick(). I'll need a test case.

[edit 2]
Nevermind, I do see a problem when pixel movement is in play.
Lummox JR resolved issue with message:
flick() did not work correctly on atoms with pixel movement.