Hi,
On Mon, 2008-06-09 at 01:45 +0200, [EMAIL PROTECTED] wrote:
That means it makes sense to work on a temporary solution before the big UI
overhaul happens?
There is no such thing as the big UI overhaul. It also does not make
sense to work on temporary solutions. Instead someone needs to
Sven Neumann wrote:
Instead someone needs to sit down
with the UI team and work out a complete solution for Save and Export,
and then start to implement it.
In that case I propose an IRC based scheduled and announced meeting on
this topic with the UI team? That way anybody who wants to can
Hi,
On Mon, 2008-06-09 at 09:32 +0300, Alexia Death wrote:
In that case I propose an IRC based scheduled and announced meeting on
this topic with the UI team? That way anybody who wants to can give
input and the output can be a complete spec for this. However the UI
team seems to have
Hi,
On Sat, 2008-06-07 at 14:51 +0200, [EMAIL PROTECTED] wrote:
The current protection mechanism for closing images is insufficient as it
doesn't
differentiate between 'saved' and 'exported'.
Yes, that is well-known and the plan is to change that at some point.
But there is no one actively
On Sunday 08 June 2008 14:28:17 Sven Neumann wrote:
On Sat, 2008-06-07 at 14:51 +0200, [EMAIL PROTECTED] wrote:
The current protection mechanism for closing images is insufficient as it
doesn't differentiate between 'saved' and 'exported'.
Yes, that is well-known and the plan is to change
Sven Neumann wrote:
Hi,
On Sat, 2008-06-07 at 14:51 +0200, [EMAIL PROTECTED] wrote:
The current protection mechanism for closing images is insufficient as
it doesn't
differentiate between 'saved' and 'exported'.
Yes, that is well-known and the plan is to change that at some point.
The current protection mechanism for closing images is insufficient as it
doesn't
differentiate between 'saved' and 'exported'.
Symptom 1:
exporting to .png requires clicking a nag-screen
Sympton 2:
closing a multi-layered image which has been exported before
doesn't give a warning about
Solution:
1) the export warning for flat file formats should be optional ('do not
show this dialog again')
2) closing images, which have not been saved to
.xcf, should trigger a warning ('you have already exported this image to
.png, but you will loose all your layering/path information if
Alexia Death writes:
I'm going to echo my support for this. The nags on saves are
counterproductive.
And often they're not even right -- e.g. The image has
transparency, flatten? shows up on anything with an alpha
channel even if every pixel is fully opaque. All those dialogs
do is train the
On Saturday 07 June 2008 20:01:17 Akkana Peck wrote:
Alexia Death writes:
I'm going to echo my support for this. The nags on saves are
counterproductive.
And often they're not even right -- e.g. The image has
transparency, flatten? shows up on anything with an alpha
channel even if every
On Sat, Jun 7, 2008 at 12:46 PM, Alexia Death [EMAIL PROTECTED] wrote:
[..]
Exactly... Witch has bitten me in the ass a few times...
That evil witch has bitten me a few times as well - even with the
pentagram drawn under my workstation ;)
Chris
___
Alexia Death wrote:
How about having a separate save option for that in the menu?
There are several feature requests about a changed export behavior:
http://bugzilla.gnome.org/show_bug.cgi?id=75328
http://bugzilla.gnome.org/show_bug.cgi?id=75459
http://bugzilla.gnome.org/show_bug.cgi?id=164709
On Saturday 07 June 2008 21:47:06 Michael Schumacher wrote:
There are several feature requests about a changed export behavior:
http://bugzilla.gnome.org/show_bug.cgi?id=75328
http://bugzilla.gnome.org/show_bug.cgi?id=75459
http://bugzilla.gnome.org/show_bug.cgi?id=164709
It has also been
On Sat, 07 Jun 2008 19:46:24 +0200, Alexia Death [EMAIL PROTECTED]
wrote:
On Saturday 07 June 2008 20:01:17 Akkana Peck wrote:
Alexia Death writes:
I'm going to echo my support for this. The nags on saves are
counterproductive.
And often they're not even right -- e.g. The image has
14 matches
Mail list logo
