Re: [Kile-devel] katepart and our shortcuts

[Michel L. <mic...@kd...>]

On Sat 04 Apr 2009, Thomas Braun wrote:
> The code  looks like:
>    // Grab Alt+1 .. Alt+4 for search mode switching
>         connect(new QShortcut(QKeySequence(Qt::ALT + Qt::Key_1), m_widget,
>                 0, 0, Qt::WidgetWithChildrenShortcut), SIGNAL(activated()),
>                 this, SLOT(onPowerModeChangedPlainText()));
>         connect(new QShortcut(QKeySequence(Qt::ALT + Qt::Key_2), m_widget,
>                 0, 0, Qt::WidgetWithChildrenShortcut), SIGNAL(activated()),
>                 this, SLOT(onPowerModeChangedWholeWords()));
>         connect(new QShortcut(QKeySequence(Qt::ALT + Qt::Key_3), m_widget,
>                 0, 0, Qt::WidgetWithChildrenShortcut), SIGNAL(activated()),
>                 this, SLOT(onPowerModeChangedEscapeSequences()));
>         connect(new QShortcut(QKeySequence(Qt::ALT + Qt::Key_4), m_widget,
>                 0, 0, Qt::WidgetWithChildrenShortcut), SIGNAL(activated()),
>                 this, SLOT(onPowerModeChangedRegularExpression()));
>
> The first odd thing is that these actions don't appear in the settings
> dialog. I think because they are not defined as proper actions.
> This is in my eyes a katepart bug.

I agree here. So we should inform the KatePart devs.

> Second what to do?
> I would prefer kick these katepart shortcuts away and stick to ours. There
> is at least in my brain a direct connection between latex and ALT+1 ;)

Maybe that's a good argument to convince the KatePart people! ;-)

Michel