#nuvie@irc.freenode.net logs for 16 Oct 2006 (GMT)

Archive Today Yesterday Tomorrow
Nuvie homepage


[08:14:22] --> Yuv422 has joined #nuvie
[09:18:18] <-- Yuv422 has left IRC (Read error: 104 (Connection reset by peer))
[09:28:29] --> Yuv422 has joined #nuvie
[09:58:25] <-- Yuv422 has left IRC (Read error: 104 (Connection reset by peer))
[10:08:02] --> Yuv422 has joined #nuvie
[10:38:02] <-- Yuv422 has left IRC (Read error: 104 (Connection reset by peer))
[10:45:04] --> Yuv422 has joined #nuvie
[11:42:26] --> SB-X has joined #nuvie
[11:43:13] <Yuv422> hi SB-X
[12:42:31] <-- Yuv422 has left IRC (Read error: 104 (Connection reset by peer))
[12:42:57] --> Yuv422 has joined #nuvie
[12:50:43] <SB-X> hi Yuv422
[12:51:29] <Yuv422> hey
[12:55:02] <SB-X> how's it going?
[12:55:09] <Yuv422> I'm good
[12:55:14] <Yuv422> how about yourself?
[12:55:24] <SB-X> I'm about to go to sleep. :)
[12:55:36] <Yuv422> I was thinking of adding the map container as the parent for objects on the map
[12:55:54] <Yuv422> then we don't need to worry about messy x,y,z vals
[12:56:03] <Yuv422> but I'm going to think about it a bit more first
[12:56:04] <SB-X> what's that? "the map container"?
[12:56:13] <Yuv422> the object lists
[12:56:20] <Yuv422> for each map location
[12:56:24] <SB-X> oh
[12:56:35] <SB-X> x,y,z vals arent that messy to me, i liked it the way it was
[12:56:58] <SB-X> you'll need to check everywhere an object's x is used to make sure it's changed to use the container or actor
[12:57:18] <SB-X> just reminding you of that :)
[12:57:31] <Yuv422> but we can't move an object on the map if the script author changes the values
[12:57:46] <Yuv422> yeah it doesn't sound good does it
[12:59:53] <SB-X> although we should already be doign that just to be safe
[13:00:02] <SB-X> that's what get_obj_container() was for
[13:00:46] <Yuv422> how do you move an object that's already on the map if you've already changed the x,y,z values in the object itself?
[13:01:06] <Yuv422> we need those values to remove the object from the map
[13:12:09] <SB-X> really?
[13:12:30] <Yuv422> well we could traverse through all the objects on the map
[13:12:35] <Yuv422> but that would take awhile
[13:12:41] <SB-X> i've been changing the x,y,z and then calling addToMap
[13:12:56] <SB-X> i probably call removeObj first too
[13:12:58] <Yuv422> on an object that's already on the map?
[13:13:03] <SB-X> yes
[13:13:08] <Yuv422> oh deaer
[13:13:10] <Yuv422> dear
[13:13:13] <Yuv422> ;-)
[13:13:17] <SB-X> is that wrong? :)
[13:13:42] <Yuv422> My guess is that would lead to doubly linked objects on the map
[13:13:43] <SB-X> i might have not called removeObj everywhere
[13:13:56] <SB-X> but maybe I did
[13:13:56] <Yuv422> as the removev call wouldn't be able to find the object
[13:14:18] <SB-X> well the correct way is to remove it before changing the location
[13:14:42] <SB-X> see how it's done in Event::pushTo
[13:14:58] <Yuv422> yeah
[13:14:59] <SB-X> i dont remember if that's correct or not
[13:15:24] <Yuv422> but the moveto methods need the values from the object itself
[13:15:35] <Yuv422> maybe we shouldn't try to do it that way
[13:21:45] <SB-X> im not sure, i'd have to see what it's going to do first
[13:21:51] <SB-X> time for bed
[13:21:51] <SB-X> cya
[13:22:11] <Yuv422> cya
[13:23:56] <-- SB-X has left IRC ("*casts gate travel*")
[13:36:14] <-- Yuv422 has left IRC ()
[14:27:38] <-- Kirben has left IRC (Read error: 110 (Connection timed out))
[15:22:23] <-- laxdragon has left IRC (Read error: 104 (Connection reset by peer))
[15:24:34] --> laxdragon has joined #nuvie
[22:01:23] --> Kirben has joined #nuvie
[22:06:22] --> Kirben_ has joined #nuvie
[22:12:47] <-- Kirben has left IRC (Read error: 145 (Connection timed out))