|
GnuCash 2.4.99
|
|
GnuCash 2.4.99
|
Dialog for handling user preferences. More...
Go to the source code of this file.
Functions | |
| void | gnc_preferences_add_page (const gchar *filename, const gchar *widgetname, const gchar *tabname) |
| void | gnc_preferences_add_to_page (const gchar *filename, const gchar *widgetname, const gchar *tabname) |
| void | gnc_preferences_dialog (void) |
Dialog for handling user preferences.
These functions are the external API available for the new user preference dialog. Preferences are now stored in GConf. This code ends up being nothing more than a pretty interface to set key/value pairs in that database. Any module may add a page (or partial page) of preferences to the dialog. These additions are done by providing the name of a glade file, and a widget in that file. If a partial page is added, the widget name provided must be that of a GtkTable containing four columns. If a full page is added, the widget name provided to this code can be any kind of widget, but for consistence it should probably be the same.
If a widget names is in the form gconf/xxx/yyy... and it is a type of widget this code knows how to handle, then the callback signals will be automatically wired up for the widget. The only fields that is required to be set in the glade file is the widget name. This code currently knows about radio buttons, check buttons, spin boxes, combo boxes, gnucash currency select widgets, gnucash accounting period widgets, and a gnucash date edit widget. (Combo boxes should not be used for less than six choices. Use a radio button group instead.)
The argument *is* a glade file, so if your code has special requirements (e.g. make one widget insensitive until another is selected) feel free to go ahead and add your own callbacks to the glade file. This code will connect any callbacks that exist in the glade file.
The tab names are user-visible strings, so they must be translated each time the tab name is accessed or specified.
Definition in file dialog-preferences.h.
1.7.4
