Re: [Gimp-user] [Request] Do not confirm closing if unsaved image was exported/overwrited ?

2012-09-16 Thread Richard Gitschlag
> From: l...@holoweb.net > To: ofn...@laposte.net > Date: Sat, 15 Sep 2012 20:23:36 -0400 > CC: gimp-user-list@gnome.org > Subject: Re: [Gimp-user] [Request] Do not confirm closing if unsaved image > was exported/overwrited ? > > On Sat, 2012-09-15 at 2

Re: [Gimp-user] [Request] Do not confirm closing if unsaved image was exported/overwrited ?

2012-09-16 Thread Ofnuts
On 09/16/2012 02:23 AM, Liam R E Quin wrote: On Sat, 2012-09-15 at 23:12 +0200, Ofnuts wrote: [...] saving as XCF "by accident" may make you lose some time, but will never make you lose data, because you can always save the JPG again from the XCF. This isn't always true. For example, after wor

Re: [Gimp-user] [Request] Do not confirm closing if unsaved image was exported/overwrited ?

2012-09-16 Thread Simon Budig
Akkana Peck (akk...@shallowsky.com) wrote: > 5. Export to (or ctrl-E, since sometimes it appears in the File menu and >sometimes it doesn't, but ctrl-E always seems to work): filename.jpg > 6. Quit > > The image is marked clean after step 3, but after step 5, the image > gets mysteriously mark

Re: [Gimp-user] [Request] Do not confirm closing if unsaved image was exported/overwrited ?

2012-09-15 Thread Liam R E Quin
On Sat, 2012-09-15 at 23:12 +0200, Ofnuts wrote: > [...] saving as XCF > "by accident" may make you lose some time, but will never make you lose > data, because you can always save the JPG again from the XCF. This isn't always true. For example, after working on a photograph I scale it down e.g

Re: [Gimp-user] [Request] Do not confirm closing if unsaved image was exported/overwrited ?

2012-09-15 Thread Akkana Peck
> On Sat, 2012-09-15 at 11:00 -0700, Akkana Peck wrote: > > Why does exporting an image mark it dirty even if it's been saved as XCF? Michael Natterer writes: > Perhaps consider the possibility that something is broken? After some experimentation and suggestions from Mitch, it turned out that it'

Re: [Gimp-user] [Request] Do not confirm closing if unsaved image was exported/overwrited ?

2012-09-15 Thread Ofnuts
On 09/15/2012 08:00 PM, Akkana Peck wrote: Ofnuts writes: If you forgot to export as JPG but saved the image as XCF, then you can reopen Gimp and produce your JPG. Trouble, yes, data loss, no. Seriously? You save an XCF copy of every JPG you crop or rescale? For about 8x-20x (depending on size

Re: [Gimp-user] [Request] Do not confirm closing if unsaved image was exported/overwrited ?

2012-09-15 Thread Michael Natterer
On Sat, 2012-09-15 at 11:00 -0700, Akkana Peck wrote: > Ofnuts writes: > > If you forgot to export as JPG but saved the image as XCF, then you > > can reopen Gimp and produce your JPG. Trouble, yes, data loss, no. > > Seriously? You save an XCF copy of every JPG you crop or rescale? > For about 8x

Re: [Gimp-user] [Request] Do not confirm closing if unsaved image was exported/overwrited ?

2012-09-15 Thread Akkana Peck
Ofnuts writes: > If you forgot to export as JPG but saved the image as XCF, then you > can reopen Gimp and produce your JPG. Trouble, yes, data loss, no. Seriously? You save an XCF copy of every JPG you crop or rescale? For about 8x-20x (depending on size and compression) the disk space? I doubt m

Re: [Gimp-user] [Request] Do not confirm closing if unsaved image was exported/overwrited ?

2012-09-15 Thread Richard Gitschlag
> Date: Fri, 14 Sep 2012 09:24:54 -0700 > From: nik-o...@yandex.ru > To: gimp-user-list@gnome.org > Subject: Re: [Gimp-user] [Request] Do not confirm closing if unsaved image > was exported/overwrited ? > > All the plugins handling non-native file formats are not built i

Re: [Gimp-user] [Request] Do not confirm closing if unsaved image was exported/overwrited ?

2012-09-15 Thread Nik Omul
* Akkana Sorry for misspelling your name, Akkana. - Nik O. Никита Омуль -- View this message in context: http://gimp.1065349.n5.nabble.com/Request-Do-not-confirm-closing-if-unsaved-image-was-exported-overwrited-tp35572p35597.html Sent from the Users mailing list archive at Nabble.com. ___

Re: [Gimp-user] [Request] Do not confirm closing if unsaved image was exported/overwrited ?

2012-09-15 Thread Nik Omul
> On 09/15/2012 12:56 AM, Akkana Peck wrote: > > Accidental work loss is the main reason I dislike the new model. > > I don't much mind the Save vs. Export split, or remembering when I > > need to type Ctrl-E vs. Ctrl-S -- but it's frustrating that I no > > longer have any way to tell whether a

Re: [Gimp-user] [Request] Do not confirm closing if unsaved image was exported/overwrited ?

2012-09-15 Thread Nik Omul
Already fulfilled in 2.8.2 1.[filename] (imported) -1.0 for imported image 2.*[filename] (imported) -1.0 for any changes made to the original 3. filename.xcf - 1.0 4.*filename.xcf -1.0 for any changes made to the original xcf 5.[Untitled] - 1.0 for newly created image New features in 2.8.4? 1.

Re: [Gimp-user] [Request] Do not confirm closing if unsaved image was exported/overwrited ?

2012-09-15 Thread Nik Omul
>>GIMP does not stand out as the only graphic editor that does it. Krita, >> Blender, Synfig, Inkscape, MyPaint - >Nope. Krita and MyPaint don't do that. >MyPaint has a Preferences setting that configures default file format >for saving. Krita just saves to whatever you choose and doesn't war

Re: [Gimp-user] [Request] Do not confirm closing if unsaved image was exported/overwrited ?

2012-09-15 Thread Maarten De Munck
Ofnuts schreef op za 15-09-2012 om 12:11 [+0200]: > On 09/15/2012 12:56 AM, Akkana Peck wrote: > > Accidental work loss is the main reason I dislike the new model. > > I don't much mind the Save vs. Export split, or remembering when I > > need to type Ctrl-E vs. Ctrl-S -- but it's frustrating that

Re: [Gimp-user] [Request] Do not confirm closing if unsaved image was exported/overwrited ?

2012-09-15 Thread Ofnuts
On 09/15/2012 12:56 AM, Akkana Peck wrote: Accidental work loss is the main reason I dislike the new model. I don't much mind the Save vs. Export split, or remembering when I need to type Ctrl-E vs. Ctrl-S -- but it's frustrating that I no longer have any way to tell whether all my JPGs have been

Re: [Gimp-user] [Request] Do not confirm closing if unsaved image was exported/overwrited ?

2012-09-15 Thread maderios
On 09/14/2012 08:37 PM, Alexandre Prokoudine wrote: On Fri, Sep 14, 2012 at 8:24 PM, Nik Omul wrote: GIMP does not stand out as the only graphic editor that does it. Krita, Blender, Synfig, Inkscape, MyPaint - Nope. Krita and MyPaint don't do that. MyPaint has a Preferences setting that conf

Re: [Gimp-user] [Request] Do not confirm closing if unsaved image was exported/overwrited ?

2012-09-14 Thread Akkana Peck
Liam R E Quin writes: > On Fri, 2012-09-14 at 00:34 +, minhsien0330 wrote: > > Dear developers: > > Can we have a new option "Do not confirm closing if unsaved image was > > exported/overwrited" ? > > It would defeat the purpose of moving Save to Export - that of avoiding > accidental work los

Re: [Gimp-user] [Request] Do not confirm closing if unsaved image was exported/overwrited ?

2012-09-14 Thread Alexandre Prokoudine
On Fri, Sep 14, 2012 at 8:24 PM, Nik Omul wrote: > GIMP does not stand out as the only graphic editor that does it. Krita, > Blender, Synfig, Inkscape, MyPaint - Nope. Krita and MyPaint don't do that. MyPaint has a Preferences setting that configures default file format for saving. Krita just sa

Re: [Gimp-user] [Request] Do not confirm closing if unsaved image was exported/overwrited ?

2012-09-14 Thread Nik Omul
>Like it or not, what file formats are available under the "Save" dialog says a lot about your program's core >purpose. Somebody said "GIMP is no longer an 'image' editor, it's now an 'xcf' editor" - I have to agree. GIMP does not stand out as the only graphic editor that does it. Krita, Blender,

Re: [Gimp-user] [Request] Do not confirm closing if unsaved image was exported/overwrited ?

2012-09-14 Thread maderios
On 09/14/2012 05:25 PM, Richard Gitschlag wrote: > Date: Thu, 13 Sep 2012 20:28:55 -0700 > From: nik-o...@yandex.ru > To: gimp-user-list@gnome.org > Subject: Re: [Gimp-user] [Request] Do not confirm closing if unsaved image was exported/overwrited ? > > It has always e

Re: [Gimp-user] [Request] Do not confirm closing if unsaved image was exported/overwrited ?

2012-09-14 Thread Richard Gitschlag
> Date: Thu, 13 Sep 2012 20:28:55 -0700 > From: nik-o...@yandex.ru > To: gimp-user-list@gnome.org > Subject: Re: [Gimp-user] [Request] Do not confirm closing if unsaved image > was exported/overwrited ? > > It has always eluded me trying to understand why so many users didn

Re: [Gimp-user] [Request] Do not confirm closing if unsaved image was exported/overwrited ?

2012-09-14 Thread Nik Omul
>close them without clicking the confirming dialog, it will save so much working time. Thank you~ Use keyboard shortcuts for closing xcf's - Ctrl+W (or click to close) then Alt+W. Really takes just fraction of a second. It has always eluded me trying to understand why so many users didn't take Sav

Re: [Gimp-user] [Request] Do not confirm closing if unsaved image was exported/overwrited ?

2012-09-13 Thread Liam R E Quin
On Fri, 2012-09-14 at 00:34 +, minhsien0330 wrote: > Dear developers: > Can we have a new option "Do not confirm closing if unsaved image was > exported/overwrited" ? It would defeat the purpose of moving Save to Export - that of avoiding accidental work loss. I would like to be told exactly