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

List:       kopete-devel
Subject:    Re: Style guide decision needed (was: [Kopete-devel] Bug#40938: behaviour change request)
From:       Thomas Zander <zander () planescape ! com>
Date:       2002-04-28 13:45:10
[Download RAW message or body]

On Sat, Apr 27, 2002 at 01:34:37AM +0200, Rob Kaper wrote:
> Dear kde-core-devel, this is a rather hot GUI issue currently discussed for
> Kopete, lacking any style guide coverage. Please read and discuss, it would
> be fruitful to address the issue and improve the style guide and have a
> decision to fall back on.
> 
> On Fri, Apr 26, 2002 at 12:54:08PM -0500, Nick Betcher wrote:
> > We've all given examples and counter examples as to which applications use 
> > Enter as their line feed or sending/executing and that proved to be useless.
> 
> I don't care what Licq, Windows ICQ version *, GAIM, Trillian or whatever
> do. I care about consistency within KDE.
> 
> > I'm just quite sick of hearing about how Enter should and shouldn't send a 
> > message, we have better things to be doing.

Within a multi-line edit or a anything else that uses the enter key for its own
purpose a modifier to access the parents widget enter functionality seems natural
for me.
I would choose for shift as that seems the normal choice to alter context, but 
control is fine with me.

Please do so.

ps. the sent button naturally has an accelerator as well right? So an [alt]-s 
would sent it as well.

-- 
Thomas Zander                                            zander@earthling.net
The only thing worse than failure is the fear of trying something new

[Attachment #3 (application/pgp-signature)]
_______________________________________________
Kopete-devel mailing list
Kopete-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/kopete-devel

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