The way I think of the workflow, I'm importing a file, editing it, and
exporting it. Overwriting the file on disk is a mere side-effect of
that workflow, and GIMP will prompt me in any case just in case I don't
want to overwrite the file.
The thing is, if I go about it a different way and export another file
to overwrite that file, I'm using the export function. Each time I then
press ctrl+E, I'm overwriting that file again and again, without even a
prompt. I don't see a meaningful difference between this workflow, and
that of importing/editing/exporting.
Jeremy Morton (Jez)
On 26/06/2011 15:14, Alexandre Prokoudine wrote:
> On Sun, Jun 26, 2011 at 6:00 PM, Jeremy Morton wrote:
>> As far as I can tell the usage pattern has already changed heavily from
>> 2.6. In 2.6 there was only one save option; now there's a save and
>> export. You've already changed that significantly.
> Yes, and there should be a better reason for going half the way back
> and introducing a crossbreed of 2.6 and 2.8 than just " it should be
> possible". I wouldn't really want to rely on arguments like "it
> doesn't make any sense", but in truth it's exactly what I think.
> "Overwrite" says exactly what it does. You can assign a shortcut to
> Alexandre Prokoudine
> Gimp-developer mailing list
Gimp-developer mailing list