Help finding an obj in view

ID:1880591
 
Jun 23 2015, 8:59 pm (Edited on Jun 23 2015, 9:23 pm)
(See the best response by Lummox JR.)
Code:
changeBuild(var/newBuild)
        var/list/builds = buildList[currentBuild]
        for(var/obj/ChangeBuild/Build in view(100))


Problem description:

Someone help refresh my memory. I'm trying to intialize a proc that looks for the "ChangeBuild" objs in view, which basically at race creation screen ( via-map) But when I start it up, and click the obj on map, it does nothing , I've chcked layers and all.

IT seems to only work if I do client.screen , but I want to find an easier way since I've already done the work of making the obj/vars.

Can anyone tell me what im doing wrong?

Whats the proper term for a for() proc for something in your view?
Jun 23 2015, 9:07 pm
It looks like you've defined a verb, is this even under /mob (but I can't tell because you didn't add that bit). In either case, I don't remember if view's first parameter is set properly in the case of verbs and you may have to add view(usr, 100) if it's a verb.
Jun 23 2015, 9:17 pm
It's a proc under this: http://prntscr.com/7kmojc
Jun 23 2015, 9:42 pm (Edited on Jun 23 2015, 9:51 pm)
Is that its own class? I haven't worked with the language for about 6 months now, so someone will have to correct me if I'm wrong but I believe the view() proc makes the src its center.

Try this:

changeBuild(var/newBuild)
        world << "[src.loc]"
        var/list/builds = buildList[currentBuild]
        for(var/obj/ChangeBuild/Build in view(100))


See if the location of the object is within view of the stuffs.
Jun 23 2015, 11:28 pm
You are doing it wrong. Character creation should be done in the client's screen. If you have to find an object that's in the client's screen, you aren't storing data that you should be.

Use variables.
Jun 23 2015, 11:49 pm
Additionally, view(100) isn't going to work because view() is range-limited.
Jun 24 2015, 4:25 am
Ah... so client screen work eh? I noticed a slight change from what I was use to back in the day of programming,

screen_loc = "0:0,0:0" <-- Lol, It's hard positioning with that for some reason, is there an easier way? It takes me forever to get em right.
Jun 24 2015, 4:32 am
I actually agree that working with those screen loc strings are a massive pain in the ass, it'd be better to think of the screen as a canvas with just absolute pixel x and y coordinates.
Jun 24 2015, 9:06 am
Best response
Maybe I can add easier-to-manage coords at some point. It'd actually be nice also to be able to get fractional coords when a map is scaled, for more accuracy.
Jun 24 2015, 9:16 am
:) Much obliged byondmin.
Jun 24 2015, 3:41 pm
In response to Lummox JR
Lummox JR wrote:
Maybe I can add easier-to-manage coords at some point. It'd actually be nice also to be able to get fractional coords when a map is scaled, for more accuracy.

Yes to this please.