<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I would like to store debugger settings such as watches, breaks,
target etc in a project file.<br>
<br>
These are not the settings that apply to a plugin in a whole but
look like being related to files<br>
user is working with, i.e. a project.<br>
<br>
After looking at project signals I was 100% sure that they are
intended to give a plugin a place to store<br>
its settings that apply to a project.<br>
<br>
Yesterday on IRC we talked about it and Matthew said that it's
better to have a distinct file.<br>
As for me, I'd better keep all session related settings in one file,
i.e. in a project and would like<br>
to ask you here what do you think about?<br>
<br>
One more question is about project signals, looks like to save
settings in a project a plugin is encouraged to<br>
add a notebook tab in "project_dialog_create" signal handler and to
save setting when this dialog is closed when processing <br>
a "project_save" signal.<br>
<br>
The GKeyFile that is passed in "project_open" signal is closed right
after sending a signal, so plugins can't use it for saving data.<br>
<br>
What if I want to write settings not using project settings dialog
that looks unsuitable for a debugger,<br>
is it correct to initialize and the save a new GKeyFile to
geany_data->app->project->file_name?<br>
<br>
Regards,<br>
Alexander<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
</body>
</html>