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

List:       kde-core-devel
Subject:    Fwd: Re: New QT tear-off menus
From:       Torsten Rahn <torsten () kde ! org>
Date:       2001-03-29 17:06:50
[Download RAW message or body]



----------  Forwarded Message  ----------
Subject: Re: New QT tear-off menus
Date: Thu, 29 Mar 2001 19:05:57 +0200
From: Torsten Rahn <torsten@kde.org>
To: kde-devel@kde.org


>> Apropos tear-off menus, did you guys find the feature that you can move
>> the mouse on a menu item, press the mouse button down and type a key
>
>   I've heard many people criticise the fact that the hide buttons are

I have been on quite a few linux-expos now and have met several
thousand people during these events. Also I have been
on quite a lot of lists and newsgroups. Up to now I haven't seen
_any_ significant number of people  asking for removing this very
handy feature by default.
Actually I know quite a _lot_ of people who love the  hide-buttons and
use them a _lot_. Judging from experience it's bad to turn such
a useful feature off by default as people won't find out that this
feature exists and won't know about it at all (At Cebit one of the
highlights of KDE 2.1 was the text-preview and most KDE 2.1-
users didn't even know about it as it was turned off by default.
Obviously none of them would have ever got the idea of turning them
on unless they were told about that feature.)

I'd like to ask to discuss such serious changes to the UI on
kde-core-devel with a _related_ topic _before_ changing them
in CVS.

>> combination?
>>
>> Another Gtk+ goody we decided to put in.
>
> nice! Now we only need to couple that to KAccel/KActions to make it
> persistent.

Yeah, hm, doesn't work properly here yet:

- it doesn't work in some cases
- currently one can enable the same shortcut for several menuitems
- the application forgets about the keybindings after being closed.
- it doesn't interoperate with the keybindings in KDE

The problems that can easily appear due to the complexity
which definately will result in clashes were
the reason why we decided against this feature back in october
1999 at the KDE-One-meeting.

Greetings,
Tackat

-------------------------------------------------------

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