Fix urandom e_config snafu. When you add new e_config properties, be sure to

bump the e_config generation.


SVN revision: 29475
This commit is contained in:
Christopher Michael 2007-04-12 03:20:42 +00:00
parent 4f1c60dba9
commit c2e24d10dd
2 changed files with 5 additions and 2 deletions

View File

@ -663,7 +663,6 @@ e_config_init(void)
e_config->winlist_pos_max_h = 320;
e_config->maximize_policy = E_MAXIMIZE_SMART | E_MAXIMIZE_BOTH;
e_config->allow_manip = 0;
e_config->border_fix_on_shelf_toggle = 0;
e_config->kill_if_close_not_possible = 1;
e_config->kill_process = 1;
e_config->kill_timer_wait = 10.0;
@ -1383,6 +1382,10 @@ e_config_init(void)
e_config->clientlist_limit_caption_len = 0;
IFCFGEND;
IFCFG(0x0116);
e_config->border_fix_on_shelf_toggle = 0;
IFCFGEND;
e_config->config_version = E_CONFIG_FILE_VERSION;
#if 0 /* example of new config */

View File

@ -54,7 +54,7 @@ typedef Eet_Data_Descriptor E_Config_DD;
/* increment this whenever a new set of config values are added but the users
* config doesn't need to be wiped - simply new values need to be put in
*/
#define E_CONFIG_FILE_GENERATION 0x0115
#define E_CONFIG_FILE_GENERATION 0x0116
#define E_CONFIG_FILE_VERSION ((E_CONFIG_FILE_EPOCH << 16) | E_CONFIG_FILE_GENERATION)
#define E_EVAS_ENGINE_DEFAULT 0