[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gimp-developer
Subject:    Re: [Gimp-developer] Isn't this behaviour unintuative?
From:       Martin Nordholts <enselic () gmail ! com>
Date:       2011-06-30 21:43:21
Message-ID: BANLkTim8W_Kch-B8TuO7uQ7JUssq=5rLVQ () mail ! gmail ! com
[Download RAW message or body]

2011/6/30 peter sikking <peter@mmiworks.net>:
> no, nothing changed in the Overwrite workflows.
>
> today's changes can be summarised as:
>
> - in the cases where before Export to was insensitive, it is
>  now sensitive and mapped to invoke Export... (the dialog)
>
> - in the cases where Overwrite blocks Export to out of the File menu,
>  the shortcut of Export to is still active and mapped to invoke Export...
>
> everything else works like before

Thanks for the clarifications, I've made this change now:

commit c73bdc097188a926f01062a009f9f22ff32dad4e
Author: Martin Nordholts <martinn@src.gnome.org>
Date:   Thu Jun 30 23:44:50 2011 +0200

    app: Make 'Export to' fall back to 'Export...'

    Make 'Export to' always sensitive (as long as there is an image at
    all). And make it fall back to 'Export...' if no export target has
    been set yet. Note that it is not necessarily visible at all times,
    sometimes 'Overwrite' shadows it. It shall still be invokable though.

    Reference:
    [Gimp-developer] Isn't this behaviour unintuative?
    http://lists.xcf.berkeley.edu/lists/gimp-developer/2011-June/026885.html


@Jeremy: Does this work better?

 / Martin


-- 

My GIMP Blog:
http://www.chromecode.com/
"GIMP 2.8 schedule on tasktaste.com"
_______________________________________________
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

[prev in list] [next in list] [prev in thread] [next in thread]