KDE/kdebase/apps/konsole/src

[Robert Knight]

> Yes, but you must provide some interface for this, too,
> otherwise, nobody can use it :)

That is what the overrideShortcut() signal mentioned in the commit is
for.  See the testShortcutOverride() method in
kdebase/apps/konsole/src/tests/PartTest.cpp for an example.

I am collecting various extensions to the TerminalInterface defined in
kdelibs and implementing them as signals and slots in the KPart for the
moment. 

Eventually (most probably KDE 4.2) when I know what people need, I will
write a replacement for the TerminalInterface interface in kdelibs.

Regards,
Robert.

On Tue, 2008-04-22 at 08:34 +0200, Christoph Cullmann wrote:
> On Tuesday 22 April 2008 08:25:24 Anders Lund wrote:
> > On Tuesday 22 April 2008, Robert Knight wrote:
> > > SVN commit 799577 by knight:
> > >
> > > Allow the terminal display's host to decide whether shortcut keypresses
> > >
> > > which are also valid terminal key sequences should be overridden and sent
> > > to the terminal instead.
> > >
> > > Default behaviour in the standalone Konsole is never to override
> > > shortcuts. Default behaviour in the terminal part is to always override
> > > shortcuts.
> > >
> > > Shortcuts which are not valid terminal key sequences (eg. because they
> > > have more than two modifiers) are never overridden.
> > >
> > > Add an overrideShortcut() signal to the Part to expose this functionality
> > > to clients.
> >
> > great! :-)
> Yes, but you must provide some interface for this, too, otherwise, nobody can 
> use it :)
> 
> cu
> Christoph
>