[Scigraphica-devel] Re: Question: prefernces autosave value vs. autosave initialization

[Conrad S. <co...@ci...>]

On Sat, 29 Sep 2001, R. Lahaye wrote:

> Conrad Steenberg wrote:
> >
> > So, to answer your question: put the call to sg_project_rescue_init() in
> > the function pythonn_init_callback(), after python_init.
>
> That's in src/sg.c. Right?
>
> I find there:
>
> ================================================================
> guint python_init_callback(gpointer data){
>
>   gtk_main_iteration_do(FALSE);
> #ifdef WITH_GNOME
>     if(gui_iconlist) gnome_app_flash(GNOME_APP(main_window), "Loading Python modules...");
> #else
> /* Do something equivalent for gtk!*/
> #endif
>
>   python_config_init();
>   sg_config_exec_commit_all();
>
>   return FALSE;
> }
> ================================================================
>
> Question: Must I add the autosave_init call just before,
> or just after the "sg_config_exec_commit_all();" ?

Neither. I think it should be in
src/python/python_int.c:commit_save_interval():

static gint commit_save_interval(SGconfig *config){
    PyObject *value;
    value=sg_config_get_value(config->name, config->group);
    sg_autosave_int=(gint)PyInt_AsLong(value);

/* Place autosave init call here */

  return TRUE;
}

This call should do all the setup etc., and invalidate a previously
existing setup (i.e. stop a previous intermittent call to save the file,
and start a new intermittent call etc.).

>
>
> By the way: what about
>
> #else
> /* Do something equivalent for gtk!*/
> #endif

The gtk version should also display a status message, just like the gnome
version.

Cheers!

Conrad

-- 
*-----------------------------------------*
| Conrad Steenberg                        |
| Caltech, Mail Code 356-48               |
| Pasadena, CA, 91125                     |
| e-mail: co...@he...          |
| Tel: (626) 395-8758                     |
*-----------------------------------------*