Hi,
I'm currently trying to port kglobalaccel in kde-runtime to frameworks. I'm
facing an issue in the file globalshortcut.cpp: it tries to access the private
header of KGlobalShortcutInfo to create a custom KGlobalShortcutInfo
object[1]. Now this looks obviously wrong and doesn't work as the p
On Wednesday 13 November 2013 07:22:18 Martin Gräßlin wrote:
> Hi,
>
> I'm currently trying to port kglobalaccel in kde-runtime to frameworks. I'm
> facing an issue in the file globalshortcut.cpp: it tries to access the
> private header of KGlobalShortcutInfo to create a custom
> KGlobalShortcutIn
2013/11/22 David Faure :
> On Wednesday 13 November 2013 07:22:18 Martin Gräßlin wrote:
>> Hi,
>>
>> I'm currently trying to port kglobalaccel in kde-runtime to frameworks. I'm
>> facing an issue in the file globalshortcut.cpp: it tries to access the
>> private header of KGlobalShortcutInfo to crea
On Friday 22 November 2013 15:39:35 Nicolás Alvarez wrote:
> Why is the daemon needed? Why can't global shortcuts handling be done
> in-process by the library?
a) not all window systems allow to read the keyboard.
b) The daemon does handling like only one application can take a global
shortcut. If
