#pentagram@irc.freenode.net logs for 23 Apr 2008 (GMT)

Archive Today Yesterday Tomorrow
Pentagram homepage


[00:08:31] <-- pupnik has left IRC (Read error: 110 (Connection timed out))
[00:21:11] --> Colourless has joined #Pentagram
[00:21:11] --- ChanServ gives channel operator status to Colourless
[00:32:49] --> Kirben has joined #pentagram
[00:32:49] --- ChanServ gives channel operator status to Kirben
[01:08:14] --> watt has joined #pentagram
[01:08:14] --- ChanServ gives channel operator status to watt
[02:31:10] --> servus_ has joined #pentagram
[02:45:39] <-- servus has left IRC (Read error: 110 (Connection timed out))
[02:53:19] --- servus_ is now known as servus
[04:36:21] <-- Kirben has left IRC ()
[07:59:08] --- pupnik_ is now known as pupnik
[08:54:05] --> Kirben has joined #pentagram
[08:54:05] --- ChanServ gives channel operator status to Kirben
[12:18:20] <-- Colourless has left IRC ("casts improved invisibility")
[13:17:06] <-- watt has left IRC ()
[13:23:51] --> Fingolfin has joined #pentagram
[13:23:51] --- ChanServ gives channel operator status to Fingolfin
[13:55:16] --> watt has joined #pentagram
[13:55:16] --- ChanServ gives channel operator status to watt
[14:23:38] <-- Kirben has left IRC (Read error: 110 (Connection timed out))
[14:53:53] <-- Fingolfin has left IRC ()
[18:17:30] <wjp> ah... that new bug report is caused by GravityProcess doing too much stuff when it terminates
[18:21:47] <wjp> I kind of wonder why I put that fall damage code in terminate()
[18:29:39] <watt> Making it happen in run as soon as we hit land instead?
[18:30:01] <wjp> yes, I don't know why I didn't do it like that in the first place
[18:32:22] <watt> It's tough to see the harm in having it in terminate and it seems like something to do only right at the end....
[18:33:34] <watt> I'm still not sure I see the problem yet.
[18:35:03] <wjp> the problem happens when a FAST_ONLY falling actor leaves the fast area
[18:36:09] <wjp> what should happen: all processes are killed, actor is deleted
[18:36:49] <wjp> what actually happens: all processes are killed, causing the GravityProcess to create a new 'fall down' animation process, actor is deleted, new anim process is executed, assertion is triggered
[18:37:21] <watt> Ah.
[18:37:29] <wjp> "oops" :-)
[18:46:00] --> pupnik_ has joined #pentagram
[18:52:45] <wjp> first commit in 2008 :/
[18:53:25] <watt> oh my.
[18:55:01] <watt> Guess we could start changing the copyright dates on files :-)
[18:57:34] <-- pupnik has left IRC (Read error: 110 (Connection timed out))
[18:58:27] <watt> looks like the last thing I was trying to play with was highlighting text in AskGump on mouseover
[18:59:22] <wjp> cool
[18:59:47] <watt> Got caught up in attempting to fix the
[19:00:01] <watt> "HACK ALERT" stuff in ButtonWidget......
[19:01:26] <wjp> ah, the font-related resizing
[19:26:00] <watt> Was moving toward having a gump_up and gump_down instead of a textwidget.
[19:27:51] <watt> I don't quite remember how far I got.
[20:15:40] --- pupnik_ is now known as pupnik
[21:44:31] <wjp> gump_up and gump_down? what do you mean by that?
[21:45:08] <wjp> (I have to go now, but will read logs tomorrow)
[21:47:05] <watt> Well... gump_up really was just textwidget, but I was figuring, that the buttos really could be handled by holding onto two gump ids - one for up one for down
[21:49:26] <watt> instead of holding the text widget id, shape_up, shape_down, frame_up, and frame_down
[21:50:09] <watt> it was pretty possible I was overdoing the whole thing.
[21:51:49] <watt> initially it was just going to be having the text widgets themselves handling a highlight color on mouse over, but that did not really work out as well as I had hoped.
[22:18:19] <-- watt has left IRC ()
[23:17:33] --> watt has joined #pentagram
[23:17:33] --- ChanServ gives channel operator status to watt
[23:56:38] --> pupnik_ has joined #pentagram
[23:58:57] --> Kirben has joined #pentagram
[23:58:57] --- ChanServ gives channel operator status to Kirben