Different "strategy" for global shortcuts

[Mark]

On Wed, Jun 13, 2012 at 10:40 AM, David Faure <faure at kde.org> wrote:

> [You keep forgetting to CC kde-frameworks-devel in your replies. Hint: use
> the
> 'A' key in kmail :-)]
>
> Using gmail ;)
I honestly didn't even notice that. Sorry list.


>  On Tuesday 12 June 2012 23:59:30 Mark wrote:
> > On Tue, Jun 12, 2012 at 8:33 PM, David Faure <faure at kde.org> wrote:
> > > But this is only for "restoring to defaults". I'm also talking about
> the
> > > case
> > > of changing the shortcut [for a global action] to something custom.
> > > With normal QActions, everything happens "inside" the QAction code.
> > > For actions with a global shortcuts (i.e. QActions registered in a
> > > KGlobalShortcutRegister class), the register has to somehow be told.
> > > You're
> > > right, a signal would do, but then it should cover both cases, and be
> > > rather
> > >
> > >  void shortcutChanged(...);
> > >
> > And that's where you're right :)
> >
> > I will try and start making some Qt code edits for all of this next week
> > and get it in shape for Qt 5.1.
> >
> > Btw, are we going to have a "inQt51" lib for frameworks now for stuff
> that
> > is going to benefit KDE (like this) but isn't going to make it for Qt
> 5.0?
>
> Yes it already exists, and is called libkdeqt5staging.
>
> "inqt5" is for stuff that is *already* in qt5, and libkdeqt5staging is for
> stuff
> that is not yet in qt5.
>

Interesting. Thank you for that.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20120613/0c81e5a8/attachment.html>