#pentagram@irc.freenode.net logs for 9 Aug 2007 (GMT)

Archive Today Yesterday Tomorrow
Pentagram homepage


[01:49:59] --> SB-X has joined #pentagram
[02:35:43] --- servus_ is now known as servus
[02:59:34] <-- SB-X has left IRC (Read error: 110 (Connection timed out))
[04:08:56] --> watt has joined #pentagram
[04:08:56] --- ChanServ gives channel operator status to watt
[06:07:27] <-- Kirben has left IRC ()
[06:09:43] --> Kirben has joined #pentagram
[06:09:43] --- ChanServ gives channel operator status to Kirben
[10:18:01] --> SB-X has joined #pentagram
[11:53:59] --> Kazinstan has joined #pentagram
[12:03:33] <-- Kazin has left IRC (Read error: 110 (Connection timed out))
[12:17:13] <-- Colourless has left IRC (Read error: 113 (No route to host))
[13:12:57] <-- Kirben has left IRC (Read error: 110 (Connection timed out))
[13:19:51] <-- watt has left IRC ()
[13:45:57] --> watt has joined #pentagram
[13:45:57] --- ChanServ gives channel operator status to watt
[13:58:07] <watt> Think I went a bit too far forward with my set of current changes..... should make it more bite-sized
[16:08:51] <watt> Ok, I'm moving the code in HIDManager that determines click or double click to GUIApp. HIDManager really only needs to be responsible for acting on those events.
[16:36:04] <wjp> ok
[16:39:00] <watt> Good, bad, indifferent?
[16:40:58] <wjp> seems to put more related code together, so good
[16:41:52] <watt> ;-)
[16:44:18] <watt> It'll enable the next few thing to be easier - I think next is to make the preempt bindings not block click & double.
[16:45:29] * wjp takes a peek at the bug tracker
[16:46:01] <wjp> I should _really_ work on the oldest bug in there
[16:46:37] <watt> after that - I think swap mouse buttons or something that will allow us to accomplish that (still not sure how I actually want to do that)
[16:47:40] <watt> "Write engine"? Nah, why would we want to do that? ;-)
[16:48:07] <wjp> "overlapping barkgumps" actually :-)
[16:49:05] <watt> yeah.... that one seem fun
[16:49:16] <wjp> main thing is deciding which data structure to use
[16:50:20] <wjp> and picking good behaviour for gumps that don't fit
[16:50:39] <wjp> and how to re-order things when a barkgump is removed
[16:51:38] <wjp> both are not overly critical, though, since they shouldn't occur often
[16:52:33] <watt> Other gumps would
[16:52:58] <watt> "re-flow" when one disappers
[16:53:00] <watt> ?
[16:53:19] <wjp> yes, in some 'stable' fashion
[16:53:27] <watt> (arg, my finger keeps hitting enter)
[16:54:01] <wjp> i.e, when three gumps are placed on top of eachother, and the bottom one is removed, the top two should both go down a bit
[16:54:05] <watt> Would they animate to their new position or simply move instantly?
[16:54:09] <wjp> (instead of only the top one going down two spots)
[16:54:21] <wjp> move instantly, I think
[16:54:24] <wjp> interesting idea though :-)
[16:54:44] <watt> instant moves are sometimes a bit jarring visually
[16:55:07] <wjp> true
[16:55:23] <watt> but animations are difficult to do
[16:55:41] <wjp> not necessarily
[16:56:13] <wjp> mainly a matter of strictly defining the meaning of the right variables
[18:04:36] <-- SB-X has left IRC (Remote closed the connection)
[20:25:32] <-- Darke2 has left IRC (Read error: 110 (Connection timed out))
[22:09:01] <-- watt has left IRC ()
[22:16:01] --> SB-X has joined #pentagram
[22:17:28] --> Darke2 has joined #pentagram
[22:40:34] --> watt has joined #pentagram
[22:40:34] --- ChanServ gives channel operator status to watt
[23:29:06] --> Colourless has joined #Pentagram
[23:29:06] --- ChanServ gives channel operator status to Colourless
[23:38:37] --> servus_ has joined #pentagram
[23:56:43] <-- servus_ has left IRC (Read error: 110 (Connection timed out))
[23:57:10] --> servus_ has joined #pentagram
[23:57:38] <-- servus has left IRC (Read error: 110 (Connection timed out))