Animating pixel_x/y

ID:1981503
 
Nov 12 2015, 8:00 pm
Not a bug
BYOND Version:509.1314
Operating System:Windows 7 Pro 64-bit
Web Browser:Chrome 46.0.2490.86
Applies to:DM Language
Status: Not a bug
This is not a bug. It may be an incorrect use of syntax or a limitation in the software. For further discussion on the matter, please consult the BYOND forums.
Descriptive Problem Summary: When attempting to animate() pixel_x/y objects inside client.screen, nothing happens.

Numbered Steps to Reproduce Problem: Add some objects to your client's screen and attempt to animate their pixel_x/y values.

Code Snippet (if applicable) to Reproduce Problem:
        MouseEntered()
            world.log << "MouseEntered() called"
            animate(src)
            animate(src, pixel_y = 8, time = 5)


Expected Results: For the animated object to animate smoothly to the specified pixel offset(s).

Actual Results: Nothing happens from what I can see.

Does the problem occur:
Every time? Or how often? Every time; successfully reproduced in a test project.
In other games? Yes.
In other user accounts? N/A
On other computers? N/A

When does the problem NOT occur? It doesn't.

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.) Tested all the way back to 508.1295 and it still occurred.

Workarounds: None.
Nov 12 2015, 8:05 pm
pixel_x,y have never had an effect on the rendering of objects in the HUD.

transform does, however.
Nov 12 2015, 8:05 pm
Kaiochao resolved issue (Not a bug)
Nov 12 2015, 8:11 pm
Huh..

Well alright. Should probably state that somewhere in the reference though.
Nov 13 2015, 12:27 am
In response to FKI
FKI wrote:
Huh..

Well alright. Should probably state that somewhere in the reference though.

I do recall this originally not being the case, but it is in the ref, so...

Under screen_loc - 
It is also possible to specify a pixel offset. Screen objects do not use pixel_x and pixel_y for this purpose, because it is intended that an object could exist on the map and in the screen object list simultaneously, so positioning must be independent. Pixel offsets are specified after a colon like this: "1:16,1:16". In this case the object is shifted to the northeast by 16 pixels.
Nov 13 2015, 1:50 am
In response to Rushnut
Ah, gotcha.