From: Jorg S. <Jor...@gm...> - 2005-11-24 12:46:06
|
Hi James, good to see you back... > I think redoing the whole format of the prefrences file was too extreme > anyway. Well, if someone comes up with an extremely better way I would definitely be for it... > I figured that it's a better > idea to work with numbered pref keys instead of just getting rid of > them. My hiatus from this did allow me to come up with an idea to make > numbered prefs work with the new prefs interface I've been working on. I > thought that the prefs functions that I was working with > (prefs_get_int_value, prefs_set_int_value, etc) might work if we had > them deal with numbered keys (i.e. the special sort tab keys) > internally. For example, take the current prototype of prefs_get_int: > > gboolean prefs_get_int_value (const gchar *key, gint *value); > > I had the idea to add another parameter to these functions, which for > now i'm calling key_number. This parameter specifies the number suffix > of a pref key (if there is one) The new prototype could look like this: > > gboolean prefs_get_int_value (const gchar *key, gint key_number, gint > *value); I would make another set of functions for numbered prefs -- no need to give out a key_number for non-numbered prefs. gboolean prefs_get_int_value_index (const gchar *key, gint key_number, gint *value) would then simply be a front-end to the existing gboolean prefs_get_int_value (const gchar *key, gint *value). > prefs_get_string("mountpoint", -1) > > Where we have a the key name, and any negative number for a key number, > so that the function would know it's dealing with a non-numbered key. Awkward ;-) Non-numbered prefs are more frequent than numbered ones... We'd also need a function to wipe out an existing numbered prefs name-space. Cheers, JCS. |