Sign up now! · Forgot password?
RSS/Atom feed identi.ca Twitter

fix gimp

This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

9 of 9 messages available
Toggle history

Please log in to manage your subscriptions.

fix gimp Name Brand 27 Dec 21:39
  fix gimp Michael Schumacher 27 Dec 21:57
   fix gimp Boudewijn Rempt 27 Dec 22:34
    fix gimp Alexandre Prokoudine 27 Dec 23:45
     fix gimp Michael Schumacher 28 Dec 00:32
      fix gimp Boudewijn Rempt 28 Dec 07:30
       fix gimp Michael Schumacher 28 Dec 10:06
     fix gimp Boudewijn Rempt 28 Dec 07:29
  fix gimp C R 27 Dec 22:07
Name Brand
2017-12-27 21:39:03 UTC (about 1 month ago)

fix gimp

yeah I just lost 3 hours of solid work because your program couldn't handle me pushing the close button when I had preferences open, instead of the "okay button" and frankly I'm extremely pissed about it. Also integrate autosave you cavemen.

Michael Schumacher
2017-12-27 21:57:40 UTC (about 1 month ago)

fix gimp

Am 27.12.2017 um 22:39 schrieb Name Brand:

Hi Name,

yeah I just lost 3 hours of solid work

that is unfortunate.

But we need to know a bit more about the issue to check if it can be replicated - to that regard, are you able to reproduce it at will, or was this a one-time occurrence? And what version of GIMP did this happen with, on what platform?

because your program couldn't handle me pushing the close button when I had preferences open, instead of the "okay button"

I assume GIMP crashed when you did this?

and frankly I'm extremely pissed about it.

There's not much we can do about that, however.

Also integrate autosave

Planned, but not as easy as you might think - https://bugzilla.gnome.org/show_bug.cgi?id=138373 has more details.

But as you are implying that you might be more intelligent (or at least educated) than us, cf.

you cavemen.

maybe you would want to work on adding autosave to GIMP?

Regards,
Michael
GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD
C R
2017-12-27 22:07:37 UTC (about 1 month ago)

fix gimp

I mean, I've definitely lost work because I forgot to hit Ctrl+S occasionally... but 3 hours? That's not something I'd personally blame on developers... nor admit to an entire mailing list. :)

Just a thought. -C

On 27 Dec 2017 9:42 pm, "Name Brand" wrote:

yeah I just lost 3 hours of solid work because your program couldn't handle me pushing the close button when I had preferences open, instead of the "okay button" and frankly I'm extremely pissed about it. Also integrate autosave you cavemen.
_______________________________________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp- developer-list
List archives: https://mail.gnome.org/archives/gimp-developer-list

Boudewijn Rempt
2017-12-27 22:34:26 UTC (about 1 month ago)

fix gimp

On Wed, 27 Dec 2017, Michael Schumacher wrote:

Planned, but not as easy as you might think - https://bugzilla.gnome.org/show_bug.cgi?id=138373 has more details.

Maybe I can add some observations... Krita has had autosave (and backup savefiles) since 2004, so we've got a bit of experience there. It came with the KOffice framework libraries that KImageShop was built on back before I joined the project.

Up to Krita 3.x, saving happens synchronously, so autosave blocks the users. But autosave only happens during natural intervals, because if the timer for autosaving goes off while the user is drawing, it gets restarted. Saving to the native file format doesn't take minutes, though.

Still, this sometimes blocks the user, and we have had complaints about that. For 4.x, we save a shallow copy of the image: i.e, when autosaving kicks in, we make a copy of the image and save that in the background. No fuss, no interruption, but a bit of added user security.

This, actually, is also how Photoshop works: one Krita developer spoke to a Photoshop developer during a recent conference and picked his brain... Photoshop makes a copy of the image for _every_ state. Any undo state is a shallow copy of the document. They do not save action data -- only copies of the image. This also explains how they created the history brush.

Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org
Alexandre Prokoudine
2017-12-27 23:45:17 UTC (about 1 month ago)

fix gimp

On Thu, Dec 28, 2017 at 1:42 AM Boudewijn Rempt wrote:

This, actually, is also how Photoshop works: one Krita developer spoke to a Photoshop developer during a recent conference and picked his brain... Photoshop makes a copy of the image for _every_ state. Any undo state is a shallow copy of the document.

Even for gigapixel panoramas?

Alex

Michael Schumacher
2017-12-28 00:32:41 UTC (about 1 month ago)

fix gimp

On 12/28/2017 12:45 AM, Alexandre Prokoudine wrote:

On Thu, Dec 28, 2017 at 1:42 AM Boudewijn Rempt wrote:

This, actually, is also how Photoshop works: one Krita developer spoke to a Photoshop developer during a recent conference and picked his brain... Photoshop makes a copy of the image for _every_ state. Any undo state is a shallow copy of the document.

For the records, I haven't received Boudewijn's message - maybe because GMX's rather strict requirements (SPF et al) are not satisfied?

Anyway, I prefer list replies instead of direct messages with list in cc. I've only cc'ed Named Brand here because they are not subscribed.

Regards,
Michael
GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD
Boudewijn Rempt
2017-12-28 07:29:03 UTC (about 1 month ago)

fix gimp

On Wed, 27 Dec 2017, Alexandre Prokoudine wrote:

On Thu, Dec 28, 2017 at 1:42 AM Boudewijn Rempt wrote:

This, actually, is also how Photoshop works: one Krita developer spoke to a Photoshop developer during a recent conference and picked his brain... Photoshop makes a copy of the image for _every_ state. Any undo state is a shallow copy of the document.

Even for gigapixel panoramas?

That's what they told us. The number of pixels shouldn't matter, since these are shallow copies -- only when a tile is changed, the actual pixel data gets copied.

That reminds me -- I don't know how Gimp handles its tiles (or scanlines) but krita has got a huge and very complicated pool and hash tables to store tiles. In photoshop, tiles are large and stored in a plain std::vector.

Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org
Boudewijn Rempt
2017-12-28 07:30:32 UTC (about 1 month ago)

fix gimp

On Thu, 28 Dec 2017, Michael Schumacher wrote:

On 12/28/2017 12:45 AM, Alexandre Prokoudine wrote:

On Thu, Dec 28, 2017 at 1:42 AM Boudewijn Rempt wrote:

This, actually, is also how Photoshop works: one Krita developer spoke to a Photoshop developer during a recent conference and picked his brain... Photoshop makes a copy of the image for _every_ state. Any undo state is a shallow copy of the document.

For the records, I haven't received Boudewijn's message - maybe because GMX's rather strict requirements (SPF et al) are not satisfied?

Yeah... I cannot send mail to most german accounts from my main email address anymore. I'm moving that to a new server, but I'm way too busy.

Anyway, I prefer list replies instead of direct messages with list in cc. I've only cc'ed Named Brand here because they are not subscribed.

Me too, but it seems this list isn't setup like that?

Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org
Michael Schumacher
2017-12-28 10:06:49 UTC (about 1 month ago)

fix gimp

Am 28.12.2017 um 08:30 schrieb Boudewijn Rempt:

On Thu, 28 Dec 2017, Michael Schumacher wrote:

Anyway, I prefer list replies instead of direct messages with list in cc. I've only cc'ed Named Brand here because they are not subscribed.

Me too, but it seems this list isn't setup like that?

It uses the RFC 2369 List-* headers.

Your mail client might have a dedicated reply function for invoking List replies - or it may not have support for them yet?

There seem to be slightly more recent versions of Alpine around, maybe you should give those a try.

Regards,
Michael
GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD