Gliding disabling when it isn't supposed to

ID:1514122
 
Mar 9 2014, 3:13 am
BYOND Version:506
Operating System:Windows 7 Pro 64-bit
Web Browser:Chrome 33.0.1750.146
Applies to:Dream Seeker
Status: Open
Issue hasn't been assigned a status value.
While in a game that uses tile movement with gliding and world.icon_size=32, go to any random object on the map and edit its bound_width to 96, then edit its bound_x to -32, and now gliding is disabled for all movables, for seemingly no good reason.

Code Snippet (if applicable) to Reproduce Problem:
mob/verb/test(atom/movable/a in world)
    a.bound_width=96
    sleep(10)
    a.bound_x=-32

Fyi, if you just edit bound_width to 96 gliding works fine, it isn't until you edit bound_x to -32 that it breaks

Expected Results:
Gliding behavior remains active because the bounding box is a multiple of 32

Actual Results:
It doesn't
Mar 9 2014, 12:56 pm
This is intended behavior. You can't modify bound_x and stay in tile/glide mode. In other words, what you want to do isn't supported.
Mar 9 2014, 3:16 pm
Theres no reason not to support it
Mar 9 2014, 4:16 pm (Edited on Mar 9 2014, 6:52 pm)
You could say there's no reason for bound_x/y at all (why not use pixel_x/y to force all objects to originate at the bottom-left of their icons?).

I think it would make more sense to allow tile size multiples of bound_x/y for tile movement, if it's not too big of a change. It would serve the same exact purpose as it does in pixel movement, after all.