My last two posts about global shortcuts got some comments i want to address now.
Whenever it comes to a discussion about the kde4 global shortcuts framework things heat up. Somehow people get really agitated if they learn how it works. Why? I don't know. It's a framework like any other. It has its ups, it has its downs. So lets have look where the problems are.
The reason i work on global and local shortcuts is because i care about them. I use heavily adapted desktop setups both under linux and windows. And that for years. Global shortcuts are an important part of these setups. Having to use the mouse makes me itchy.
Over this i time developed a global shortcuts setup that works for both on windows and linux. I tend to get angry if one of them doesn't work. Using them for more than five years makes me trying to use them unconsciously even if i know they don't work. Which frustrates me.
Just a short note that i commited a change to kdebase reenabling shortcut support in kmenuedit. It's now possible again to assign a global shortcut to an application in kmenuedit. It was possible for some time in kshortcuts but it looks like no one noticed.
Please tell me if you have problem with that feature.
The gui side in khotkeys is not yet finished but i'm working on it. If someone would like to help polish that contact me.
MikeWhen working with shortcuts you sooner or later encounter the problem of having action shortcut conflicts. Action shortcuts conflict if they are active in the same context and are either identical or one is part of the other (ambiguous).
Conflicting shortcuts in a kde4 application trigger some very frustrating behaviour: None. Nothing happens. No action is triggered. QShortcutEvents has a property to check if an event is ambiguous. QAction::event() checks if it is set and then silently drops the event. No signal is emitted.
There are three sources for conflicting shortcuts in KDE applications: shortcuts, standard shortcuts (KStandardAction and KStandardShortcuts) and global shortcuts. Global shortcuts are out of scope for this post.
My name is Michael Jansen. I'm 35 years old and a freelance config manager/developer from germany.
You can find my homepage at http://michael-jansen.biz . Only posts related to kde will be syndicated here.
I started contributing to kde in January 2008. That's pretty lame because i wanted to do that for some years. Developing is some kind of hobby for me since my real life jobs started to be more configuration management related.
This is my list of must have Firefox extensions. These are the extensions i can't live without. I put them here for myself so i'm able to setup new firefox installations properly without great hassle.
This is just my list of useful extensions. There are many more out there.
The source code repository of KDE is big. So big that it's nearly impossible to find all the gems hidden in there. One of these useful little tools is the kdeaccounts plugin from the kdesdk module. If you ever wondered how to find out the email address of a particular kde developer, look no further.
The plugin adds all active kde developers email addresses to your kde addressbook. Check it out: kdesdk/kdeaccounts-plugin
A week ago i started hacking on a python based kdesvn-build substitution. I did that for two reasons:
Today i proudly present build-tool. It's not nearly feature complete but it does it's job. And i would like to get some feedback. Keep in mind that it's alpha quality. Noone else but me used it until now. So expect some failures.