[00:22:44] --> Kirben has joined #pentagram
[00:22:44] --- ChanServ gives channel operator status to Kirben
[00:52:44] <-- Fingolfin has left IRC ("42")
[03:15:45] --- ChanServ removes channel operator status from DarkeZzz
[11:51:49] --> Fingolfin has joined #pentagram
[11:51:49] --- ChanServ gives channel operator status to Fingolfin
[13:11:55] --> Colourless has joined #Pentagram
[13:11:55] --- ChanServ gives channel operator status to Colourless
[13:12:22] <Colourless> hi
[13:16:59] --> WW^ has joined #pentagram
[13:17:03] <WW^> Author PHP pages (Query and Insert) that access a pre-designed compact disk MySQL database
[13:18:08] <-- WW^ was kicked from #pentagram by Colourless (huh wtf?)
[13:22:17] <-- Fingolfin has left IRC ("42")
[13:46:04] <Kirben> Could you change the window title of program to Pentagram ? it is still listed as just SDL_app
[13:52:50] <Colourless> yes, eventually :-)
[14:01:27] <DarkeZzz> It's probably easier just to add a question/answer to the faq, like, "When are you going to change the title of the pentagram window to something appropriate? Sometime.", then it is to actually change the title. *grin*
[14:04:23] <Colourless> yes indeed
[14:04:42] <Colourless> to change the title, someone has to look up what the sdl api call that needs to be made
[14:04:47] <DarkeZzz> "Umm... why?" "Most other games hide the fact they're sdl based somewhere in their documentation, (which no-one ever bothers to read *anyway*), we like to come out and say that pentagram wouldn't *exist* without sdl, and this is the way we say that."
[14:05:01] <Colourless> then modify pentagram, AFTER working out the appropriate spot to update it
[14:05:38] <DarkeZzz> That's going to be an interesting challenge in itself. *grin* Maybe we should spawn a process to do that?
[14:05:52] <Colourless> hmm, i don't know
[14:06:36] <Colourless> the problem is
[14:06:55] <Colourless> we can't differentiate between pentagram itself, and any other GUIApp yet
[14:06:58] <DarkeZzz> What's scary, is the way we're trying to do things in pentagram, is that idea *does* make just a little sense. *grin*
[14:07:36] <Colourless> you see, to update the title to Pentagram, we need to separate the Pentagram specific parts from GUIApp :-)
[14:07:55] <Colourless> cause that is the 'obvious' place to update the title
[14:08:04] <DarkeZzz> So we need to write a usecode compiler, to compile a basic autoexec script, that we run whever pentagram starts up to setup local state?
[14:08:13] <DarkeZzz> Such as program titles?
[14:08:32] <Colourless> yes, sounds about right :-)
[14:08:45] <DarkeZzz> After all, this is a mostly generic engine, so we *should* be seperating any data bits, into the data sections. *grin*
[14:09:01] <Colourless> we pass a usecode string to a usecode function, that we update to the title
[14:09:42] <DarkeZzz> That way once we get past all the menu stuff (after user has selected the appropriate game) we could set the title to "Ultima 8: Pentagram" or "Pentagram: No Regret", or whatever.
[14:09:46] <Colourless> of course, i have no idea if that will work :-)
[14:10:03] <DarkeZzz> Yeah, it would. *grin*
[14:10:12] <DarkeZzz> You'd need an UpdateWindowTitle intrinsic though. *grin*
[14:10:20] <Colourless> modifying strings passed to usecode function? can that be done?
[14:10:28] <Colourless> no obviously not if you need an intrinsic to do i
[14:10:28] <Colourless> t
[14:11:23] <Colourless> of course, the title could just be set in the game config file....
[14:11:28] <DarkeZzz> Eh? I'd have it the other way around. You'd end up with the "pentagram" string imbedded in the usecode function, which would then push it on the stack and call the appropriate UpdateWindowTitle intrinsic. Though I *am* almost alseep at the keyboard...
[14:12:41] <DarkeZzz> You'd have to convert the string, to a proper usecodestring before modifying it in a usecode function, then when passing it back out of the usecode function you would have to convert it back to a normal std::string or whatever.
[14:13:14] <DarkeZzz> For that matter you have to convert it to a usecodestring to even pass it to a usecode function. *grin*
[14:13:27] <Colourless> how exactly do usecode string pointers work?
[14:14:11] <Colourless> nm
[14:14:12] <DarkeZzz> They're essentially a 16bit offset within a global memory chunk.
[14:14:31] <DarkeZzz> No problem. *grin*
[14:14:38] <DarkeZzz> Really should sleep now. *grin* Night!
[14:42:35] --> Fingolfin has joined #pentagram
[14:42:35] --- ChanServ gives channel operator status to Fingolfin
[14:46:56] <Colourless> hi
[15:22:55] --> wjp has joined #pentagram
[15:22:55] --- ChanServ gives channel operator status to wjp
[15:23:22] <wjp> hi
[15:49:31] <-- Colourless has left IRC (Read error: 110 (Connection timed out))
[16:35:18] --> eldron has joined #pentagram
[16:54:22] --> Colourless has joined #Pentagram
[16:54:25] --- ChanServ gives channel operator status to Colourless
[16:58:43] <-- Kirben has left IRC (Read error: 104 (Connection reset by peer))
[17:04:12] <wjp> wb :-)
[17:21:44] <Fingolfin> yo man! da Kirben in da house!
[17:34:23] <wjp> uh, actually Kirben just left :-)
[17:39:54] <Colourless> hehe
[17:40:44] <wjp> hmm.. "Talk to us, before annoying developers." <-- parse error
[17:41:05] <Colourless> you see any 'developing' being done?
[17:41:11] <Colourless> if so, please point it out :-)
[17:41:28] <wjp> oh.. you mean before like in 'earlier'?
[17:42:14] <Colourless> hmm, i note discussion....
[17:44:52] <wjp> hm?
[17:45:33] <Colourless> nm, obviously we are both being confused by each other
[17:45:44] <wjp> so it would seem :-)
[19:12:50] <Colourless> i'm off
[19:12:55] <Colourless> cya
[19:12:55] <-- Colourless has left IRC ("casts invisibility")
[21:46:48] <-- wjp has left IRC ("Zzzz...")
[22:21:37] --> SB-X has joined #pentagram