screen limits

ID:1425155
 
Nov 18 2013, 8:07 pm
Redundant
Applies to:
Status: Redundant
This feature has already been implemented, or is already achievable with existing methods.
Currently, when an object's screen_loc places it outside the boundaries of client.view, the screen's limits are altered to accommodate it. Request: A set of variables to indicate the limit to which the view is allowed to stretch. e.g.

client
    
    screen_limit_min_x = 1
    screen_limit_max_x = 10
    
    screen_limit_min_y = 1
    screen_limit_max_y = 10
    
    verb/test()
        var/obj/o = new
        o.screen_loc = "0,0"
        screen += o // the view will not be altered to accomodate o due to the limiting vars
Nov 18 2013, 9:12 pm
I'm a bit busy right now, but can you do me a favor and test these two scenarios:


world
    icon_size = 32
    New()
        world.maxx = 50
        world.maxy = 50
        world.maxz = 1
client
    view = "10x10"
    verb
        test1()
            src.screen.Cut(1,0)
            src.screen += new/obj/test1()
        test2()
            src.screen.Cut(1,0)
            src.screen += new/obj/test2()
obj
    test1
        screen_loc = "1:352,1"
    test2
        screen_loc = "1,1"
        transform = matrix(1,0,352,0,1,0)


Let me know if the behavior is consistent for these two cases, would you?
Nov 18 2013, 9:50 pm
Cheers. The view doesn't stretch in those two scenarios.
Nov 19 2013, 12:14 am
In response to Metamorphman
Metamorphman wrote:
Cheers. The view doesn't stretch in those two scenarios.

Yeah, I'd figured out the transform one when the feature first came out. The large pixel offset one, though, I hadn't tested thoroughly, as I only use it in multiple-map scenarios.

Seems to make sense, though, in a weird sort of way.

To be honest, I'm not sure why anybody would use the 4:16 format when 1:144 would work just fine, and in some cases, be preferable.
Nov 21 2013, 11:10 am
Lummox JR resolved issue (Redundant)