Well, why not?

in my case, it was because i needed to edit the gradients and then
export them to another machine - i was installing a web site. i hope
you'll agree that this has little to do with whether the GIMP is running.

also, i was trying to learn the gradient file format, and without
being able to see my changes right away, it was a challenge.

In the 1.3 tree the functionality to save and revert is already
foreseen but not yet implemented. This should be completed before the
next release. We won't change this behaviour in the 1.2 tree however.

fair enough, thanks Sven.

Bumping a bunch of enhancement requests which will not be done by the feature
freeze to Future. 

Dave.

The functionality is almost there. Setting back to 1.3.

Hi,

This may be a silly question, but what's wrong with  the trivial
implementation 

static void
gimp_data_editor_save_clicked (GtkWidget      *widget,
                               GimpDataEditor *editor)
{
  GimpData *d = gimp_data_editor_get_data(editor);
  GError *e = NULL;
  gimp_data_save(d, &e);
  if (e != NULL)
  {
    // do stuff with error
  }
}
                                                                     
          
Sven mentioned that there was a problem with doing this trivially, but
I can't see one. What was the problem?

Cheers,
Dave.

2003-11-10  Dave Neary  <bolsh@gimp.org>
 
        * app/widgets/gimpdataeditor.c: Implement save button. Partially
        addresses bug #116606.


This gives a workaround - when you click the save button the data
being editted is saved instantaneously.

To have the editor save data on closure of the window, we need to
over-ride the _destroy() function for gimpeditor, I think, but I may
be wrong about that. 

Is there any way to get at and save dirty data in gimp_editor_destroy()? 

Dave.

Fixed in HEAD:

2003-11-11  Dave Neary  <bolsh@gimp.org>
 
        * app/widgets/gimpdataeditor.c: Save data before disposing of
        it when closing the dialog. Closes bug #116606.