Good to know that the messages are harddly ever shown and that it isn't
anything to worry about since one wouldn't always be able to read the entire
message on narrow image windows if they don't scroll.
I just wanted to inquire about it now while the change was fresh. Otherwise
someone would b
Hi,
On Mon, 2006-10-02 at 23:56 -0400, Kevin Cozens wrote:
> mitch wrote:
> > I just comitted a change that moves all tool error messages that
> > can happen when clicking the image to the image window's statusbar,
> > using the new gimp_statusbar_push_temp() API.
>
> I will have to see how this
mitch wrote:
I just comitted a change that moves all tool error messages that
can happen when clicking the image to the image window's statusbar,
using the new gimp_statusbar_push_temp() API.
I will have to see how this works in practice. I have some doubts as to
whether this is a good idea. F
On Sun, Oct 01, 2006 at 12:04:47PM -0400, Christopher Curtis wrote:
> I hope I'm not showing my lack of UI skills here, but:
>
> On 9/26/06, Carol Spears <[EMAIL PROTECTED]> wrote:
> >On Tue, Sep 26, 2006 at 02:17:34PM -0700, William Skaggs wrote:
> >> >"Indexed images are not currently supported.
I hope I'm not showing my lack of UI skills here, but:
On 9/26/06, Carol Spears <[EMAIL PROTECTED]> wrote:
On Tue, Sep 26, 2006 at 02:17:34PM -0700, William Skaggs wrote:
> From: Michael Natterer <[EMAIL PROTECTED]>
>
> >While doing so I noticed they are all bad and inconsistent.
> >"Indexed ima
Hi,
On Thu, 2006-09-28 at 13:30 +0200, Raphaël Quinet wrote:
> These informational messages would be displayed in the status bar without
> the "warning" icon that is currently used (we could use some "info" icon
> although using no icon is probably better if we want the warnings to be
> noticed e
Raphaël Quinet wrote:
I am not sure about "does not operate" vs. "cannot manipulate", but I
I prefer "operate" to "manipulate". An alternatives would be "can not work
with indexed images" or "can not use indexed images"
--
Cheers!
Kevin.
http://www.interlog.com/~kcozens/ |"What are we goin
On Wed, 27 Sep 2006 23:50:24 +0200, Michael Natterer <[EMAIL PROTECTED]> wrote:
> On Wed, 2006-09-27 at 21:25 +0200, Raphaël Quinet wrote:
> > On Wed, 27 Sep 2006 21:03:30 +0200, Sven Neumann <[EMAIL PROTECTED]> wrote:
> > > How do we handle the statusbar being invisible? Perhaps the statusbar
> >
On Wed, 2006-09-27 at 21:25 +0200, Raphaël Quinet wrote:
> On Wed, 27 Sep 2006 21:03:30 +0200, Sven Neumann <[EMAIL PROTECTED]> wrote:
> > On Tue, 2006-09-26 at 23:02 +0200, Michael Natterer wrote:
> > > I just comitted a change that moves all tool error messages that
> > > can happen when clicking
I'll let the native English speakers decide if "does not operate on"
is better than "cannot manipulate", but otherwise I'm ready to add the
tests for the layer masks or channels.
"does not operate on" seems like a developer's or mathematician's comment,
not language for the end-user who thi
On Wed, 27 Sep 2006 21:03:30 +0200, Sven Neumann <[EMAIL PROTECTED]> wrote:
> On Tue, 2006-09-26 at 23:02 +0200, Michael Natterer wrote:
> > I just comitted a change that moves all tool error messages that
> > can happen when clicking the image to the image window's statusbar,
> > using the new gim
Hi,
On Tue, 2006-09-26 at 23:02 +0200, Michael Natterer wrote:
> I just comitted a change that moves all tool error messages that
> can happen when clicking the image to the image window's statusbar,
> using the new gimp_statusbar_push_temp() API.
How do we handle the statusbar being invisible?
Hi,
On Wed, 2006-09-27 at 15:50 +0200, Raphaël Quinet wrote:
> I am not sure about "does not operate" vs. "cannot manipulate", but I
> agree with the usage of "images" instead of "layers": talking about
> images makes it more likely that the user will think about changing
> the image mode. In th
On Wed, Sep 27, 2006 at 03:50:28PM +0200, Rapha?l Quinet wrote:
> On Tue, 26 Sep 2006 15:00:16 -0700, Carol Spears <[EMAIL PROTECTED]> wrote:
> > On Tue, Sep 26, 2006 at 02:17:34PM -0700, William Skaggs wrote:
> > > From: Michael Natterer <[EMAIL PROTECTED]>
> > >
> > > >While doing so I noticed t
On Tue, 26 Sep 2006 15:00:16 -0700, Carol Spears <[EMAIL PROTECTED]> wrote:
> we were discussing a few changes to this on the irc,
>
> On Tue, Sep 26, 2006 at 02:17:34PM -0700, William Skaggs wrote:
> > From: Michael Natterer <[EMAIL PROTECTED]>
> >
> > >While doing so I noticed they are all bad
we were discussing a few changes to this on the irc,
On Tue, Sep 26, 2006 at 02:17:34PM -0700, William Skaggs wrote:
> From: Michael Natterer <[EMAIL PROTECTED]>
>
> >While doing so I noticed they are all bad and inconsistent.
>
> >"Indexed images are not currently supported."(heal)
>
> Hea
From: Michael Natterer <[EMAIL PROTECTED]>
>While doing so I noticed they are all bad and inconsistent.
Here is what I think should happen:
>"No brushes available for use with this tool." (brush core)
>"No patterns available for this operation." (clone)
doesn't matter, these will almo
Hi all,
I just comitted a change that moves all tool error messages that
can happen when clicking the image to the image window's statusbar,
using the new gimp_statusbar_push_temp() API.
While doing so I noticed they are all bad and inconsistent.
Here is the full list, grouped by reason of the e
18 matches
Mail list logo
