RSS/Atom feed Twitter
Site is read-only, email is disabled
  1. Chat
  2. Useful links
  3. Polls

Featured content

API for time of last change vs. last export

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.

3 of 3 messages available
Toggle history

Please log in to manage your subscriptions.
API for time of last change vs. last export Akkana Peck 18 Nov 01:12
  API for time of last change vs. last export Alexia Death 19 Nov 08:10
   API for time of last change vs. last export Guillermo Espertino (Gez) 24 Nov 21:32
Akkana Peck
2012-11-18 01:12:51 UTC (about 12 years ago)

API for time of last change vs. last export

On the thread-which-shall-be-nameless, when folks were asking for a way to quit GIMP without being prompted to save files that had already been exported, Alexia wrote:

Oh, let me throw up this idea for you - you do not need a fork, just a script to override the default close... Very easy to install, maintain and distribute. No fork needed.

Alexia, how? I looked into it, but couldn't figure out any way to do it.

There's gimp-image-is-dirty to check whether an image has been changed since the last XCF save -- is there a similar flag for checking whether an image has been changed since the last export? There's gimp-image-get-exported-uri, but that only tells you whether the image has *ever* been exported, not whether it's been exported since the last image change.

If you could get the time of the last image change, you could compare it to the last modified date of the export file, but I don't think there's a GIMP call to get that either.

Suggestions?

...Akkana

Alexia Death
2012-11-19 08:10:01 UTC (about 12 years ago)

API for time of last change vs. last export

On Sun, Nov 18, 2012 at 3:12 AM, Akkana Peck wrote:

On the thread-which-shall-be-nameless, when folks were asking for a way to quit GIMP without being prompted to save files that had already been exported, Alexia wrote:

Oh, let me throw up this idea for you - you do not need a fork, just a script to override the default close... Very easy to install, maintain and distribute. No fork needed.

Alexia, how? I looked into it, but couldn't figure out any way to do it.

Good question. I asked mitch if this is possible and he said yes. My idea was to override the close, but now that I look at it, the problem is, that you seem to be unable to get the display for user opened image to close it...

--Alexia
Guillermo Espertino (Gez)
2012-11-24 21:32:46 UTC (about 12 years ago)

API for time of last change vs. last export

El 19/11/12 05:10, Alexia Death escribi:

On Sun, Nov 18, 2012 at 3:12 AM, Akkana Peck wrote:

On the thread-which-shall-be-nameless, when folks were asking for a way to quit GIMP without being prompted to save files that had already been exported, Alexia wrote:

Oh, let me throw up this idea for you - you do not need a fork, just a script to override the default close... Very easy to install, maintain and distribute. No fork needed.

Alexia, how? I looked into it, but couldn't figure out any way to do it.

Good question. I asked mitch if this is possible and he said yes. My idea was to override the close, but now that I look at it, the problem is, that you seem to be unable to get the display for user opened image to close it...

Maybe a good compromise to put an end to this discussion (and leaving almost everybody happy) would be to expose in the API all the variables involved in the save/export procedure, not only the close dialog, so anybody can create a script that brings back the old behavior without patching or modifying the default install. That would avoid the need of a fork, and a plugin to revert to the old behavior would be around the corner. More importantly, the default workflow proposed by the development and UI teams wouldn't be affected.

G.