#pentagram@irc.freenode.net logs for 17 May 2004 (GMT)

Archive Today Yesterday Tomorrow
Pentagram homepage

[01:30:34] <-- sbx has left IRC ()
[04:06:51] <watt> think we need a method to remove keys from the SettingManager. keys that are unbound by the controls gump need to be either removed in saveBindings or set to an empty string (or something else)
[06:21:22] <-- Sectus has left IRC ("Leaving")
[07:54:41] <-- Darke has left IRC ("Inficio-Infeci-Infectum")
[08:15:35] --> Colourless has joined #Pentagram
[08:15:35] --- ChanServ gives channel operator status to Colourless
[08:16:01] <Colourless> hi
[08:47:53] <wjp> hi
[08:58:43] --> Darke has joined #pentagram
[14:14:47] <-- Kirben has left IRC ("System Meltdown")
[15:05:33] <-- watt has left IRC ("using sirc version 2.211+KSIRC/1.3.10")
[15:59:06] --> Sectus has joined #pentagram
[16:20:41] <-- wjp has left IRC (Read error: 104 (Connection reset by peer))
[16:24:13] --> wjp has joined #pentagram
[16:24:13] --- ChanServ gives channel operator status to wjp
[16:36:59] <-- Sectus has left IRC (Read error: 104 (Connection reset by peer))
[16:37:13] --> Sectus has joined #pentagram
[17:03:54] <-- wjp has left IRC (Remote closed the connection)
[17:16:24] --> watt has joined #pentagram
[18:09:47] <-- Colourless has left IRC ("brb")
[18:13:24] --> Colourless has joined #Pentagram
[18:13:24] --- ChanServ gives channel operator status to Colourless
[18:21:42] --> wjp has joined #pentagram
[18:21:43] --- ChanServ gives channel operator status to wjp
[18:34:24] --> sbx has joined #pentagram
[18:52:45] <-- sbx has left IRC ()
[20:31:36] <watt> Would it be a good idea to have the HIDManager avoid needing a saveBindings method by automatically save them when rebound?
[20:46:04] <wjp> hm, we need to think about that more generally, I guess
[20:46:28] <wjp> do we want to save the .ini file(s) whenever and as soon as they're changed?
[20:47:33] <Colourless> I wouldn't
[20:47:44] <Colourless> but that's just me
[20:47:51] <Colourless> it doesn't really matter
[20:48:13] <Colourless> the reason i wouldn't is purely because of display settings
[20:48:46] <Colourless> but if things are done right, it doesn't matter
[20:49:18] <Colourless> you just update the settings after the conformation the new settings are ok
[20:51:46] <watt> I figure it would be nice to save the call to saveBindings and since we don't write the settings to the file until the settingManager is told too, It might make sense
[20:51:51] <Colourless> of course rewriting the config file with ever update of a setting is... could be considered to be a rather poor way of doing things
[20:54:17] <wjp> we could save when closing the config gump
[20:55:05] <wjp> when changing settings through the console I'd automatically save (if/when we allow that)
[20:55:57] <Colourless> i haven't quite figured out how to do setting changes thought the console yet :-)
[20:56:54] <watt> btw, I'm adding an unset(key) to the conf system for removing keys.
[20:56:54] <wjp> could simply wrap SettingManager::set/get
[20:56:55] <Colourless> giving the ability to change all settings thought the console would be crazy
[20:57:05] <wjp> heh, maybe :-)
[20:57:11] <Colourless> s/thought/though/
[20:57:20] <wjp> watt: be sure to consider what happens to comments
[20:57:21] <Colourless> uh
[20:57:26] <Colourless> s/though/through/
[20:57:45] <wjp> and what happens when a key is set in another file than the top level one
[20:58:51] <watt> I figure the comment for the keyValue would likely just be removed.
[20:59:38] <Colourless> an idea for console settings would be to have a 'Console::cvarAdd()' like function that you would probably call when you set the default value for a config setting
[20:59:41] <watt> although.. It could possibly be moved to a different key.... I dunno
[21:00:02] <Colourless> you'd only do it for settings you want to be allowed to be set in the console
[21:00:04] <wjp> currently I'm somewhat assuming that comments are above the key/section they belong to
[21:00:08] <wjp> Colourless: makes sense
[21:00:21] <wjp> things like cheat/debug vars, I guess
[21:00:48] <wjp> some settings we don't necessarily want in the config gumps but which should be accessible at runtime
[21:01:16] <Colourless> yeah. The thing is you get a problem where how do you get the setting used everywhere
[21:02:03] <Colourless> attempting to re-access a config value every frame to check to see if it's changed from the console isn't a great idea
[21:03:14] <wjp> well, I did implement callbacks for a reason :-)
[21:03:37] <Colourless> you did...
[21:03:49] <Colourless> cool
[21:04:17] <Colourless> that simplifies things :-)
[21:09:29] <watt> should unset in SettingManager should probably call the callBack and then remove it?
[21:11:47] <wjp> no, remove first, then call callback
[21:12:28] <Colourless> just a note, bindings will NOT be directly exposed in the console
[21:12:34] <Colourless> it will just be too icky
[21:13:02] <Colourless> will set them using listbinds, bind and unbind commands
[21:13:26] <watt> Agreed.
[21:13:54] <watt> wjp:should it remove the callback?
[21:14:04] <watt> thinking no...
[21:18:32] <watt> Colourless: Want me to write the unbind and listbinds commands while I'm still mucking about in the HIDManager
[21:18:34] <watt> ?
[21:18:44] <Colourless> if you want
[21:19:25] <Colourless> doesn't matter who does it :-)
[21:22:03] <wjp> watt: no, it shouldn't remove the callback
[21:27:16] <watt> ok
[22:14:54] <wjp> time for me to go
[22:14:58] <wjp> g'night
[22:15:02] <Colourless> night
[22:15:04] <watt> night
[22:15:06] <Colourless> i should go too :-)
[22:15:08] <Colourless> morning :-)
[22:15:09] <-- Colourless has left IRC ("casts invisibility")
[22:52:34] --> sbx has joined #pentagram