Re: Keyboard shortcut enhancement.
On Samstag, 15. Februar 2014 00:48:26 CEST, p.kubik...@gmail.com wrote: On Friday 14 of February 2014 17:20:44 Michael Jansen wrote: Window Trigger Action == This is more or less broken since kde4 afaik (never used it myself). This is the first candidate to go. Does edge snapping depend on Window Trigger Action or it's done without this mechanism? Also I don't understand why does it belong to the khotkeys. Of course it's connected but I not that much. Window Trigger Action allows you to bind de/activation and un/mapping of windows to random commands resp. to dbus calls or sending keyboard input. At least sending keyboard input virtually broken (no matter how it's triggered) This has nothing to do with window movement or active screen edges. Cheers, Thomas Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Keyboard shortcut enhancement.
On Friday 14 of February 2014 17:20:44 Michael Jansen wrote: > Global Shortcuts > == > > These can not go. They are relied upon for example by kmenuedit to set > shortcuts for applications. This functionality could be incorporated into > kglobalaccel and that was the last thing on my to do list before life made > me leave real kde contributing behind. I mean here global key press -> > Start an app. What to do with key press -> (make a dbus call/send keyboard > input) has to be discussed. > Window Trigger Action > == > > This is more or less broken since kde4 afaik (never used it myself). This is > the first candidate to go. > > In KDE3 khotkeys was much more capable but the same mess as today usability > and gui wise. > > Mike Does edge snapping depend on Window Trigger Action or it's done without this mechanism? Also I don't understand why does it belong to the khotkeys. Of course it's connected but I not that much. On Friday 14 February 2014 13:46:55 Thomas Lübking wrote: > An alternative might be a GUI for xbindkeys and a resp. wayland pendant (if > such exists), but i guess kglobalaccel would have to be moved to such > backend in general. Hotkeys (here global shortcuts) are very important component of DE and I think they require some special care. If it is so difficult to find a maintainer maybe it's a good idea to find some unified daemon and create a backend. Might be difficult to make it work with the rest of code but possibly worth it. >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
New to open source
I am completely new to open source. I have a keen interest in learning it. Can anybody please help me? >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Thanks for your help and please go on! (with Link ;-)
Morning Slightly embarrassing but here is the link: http://survey.kde.org/index.php/249736/lang-en Thx Mario >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Keyboard shortcut enhancement.
On Friday 14 February 2014 13:46:55 Thomas Lübking wrote: > Am Freitag, 14. Februar 2014 schrieb Andreas Pakulat : > > In particular I'm using it to start my preferred browser and to control > > my preferred mp3 player. The latter is a cli-tool so it has no global > shortcuts support but it has invocations which talk to the running instance > and can do play, pause etc. > > > That part of khotkeys has been working for me from KDE 4.2 up until now > > (4.11 here), so no idea why it is considered to be 'broken'. > > I think, the only part severely "broken" is triggering random input events. > > On non non-focused windows that requires xsendevent (for kbd input at > least) which noeadays seem largely ignored by clients. This might be > different with wayland (ability to discriminate a synthetic event in > general?), but i guess it's a security concern.?. > > An alternative might be a GUI for xbindkeys and a resp. wayland pendant (if > such exists), but i guess kglobalaccel would have to be moved to such > backend in general. Ok ... i now notice i should have been much clearer. So here the email i should have sent the first time. khotkeys is a mixed bag. We have Global Shortcuts == These can not go. They are relied upon for example by kmenuedit to set shortcuts for applications. This functionality could be incorporated into kglobalaccel and that was the last thing on my to do list before life made me leave real kde contributing behind. I mean here global key press -> Start an app. What to do with key press -> (make a dbus call/send keyboard input) has to be discussed. Mouse Gesture Action = Its kinda unmaintained but still kinda works. There are certain bugs that make random stuff in other apps fail if mouse gesture is enabled. There are some bugs on bugs.kde.org. There are a lot of wishes on bugs.kde.org. There is a great standalone alternative called easystroke. Perhaps the effort should go into making easystroke a first class citizen on kde instead of maintaining our own halb broken implementation. The biggest problem is that mouse gestures should belong into a application like shortcuts and should not be global. There were some effort at making qt support mouse gestures (like key triggers) but i don't think they gone anywhere. khotkeys is so complicated and able to break other apps because it does quite some global x key event listening and replaying while trying to determine if the app that has focus has active mouse gestures and if there is currently a gesture being made. Window Trigger Action == This is more or less broken since kde4 afaik (never used it myself). This is the first candidate to go. In KDE3 khotkeys was much more capable but the same mess as today usability and gui wise. Mike >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Thanks for your help and please go on!
First and foremost I'd like to thank all the people who already took some time and participated in the questionnaire [1] for my diploma thesis and KDE. But it's not over yet (last chance is on 25th of February) and we still need more data and as a member of KDE I know we can do more and better. I got some feedback about the length of the questionnaire [1] and that some questions (mostly the once at the beginning of the questionnaire [1] about the 12 different tasks) are quite abstract and difficult. But please try it, try your best and take the time and brain power. The remaining part of the questionnaire [1] (after these two pages with the tasks questions) is quite easy and quickly done. So if you already started the questionnaire and gave up then or needed to run for something else: no problem, you can reopen the questionnaire and continue where you left. And don't forget the chance to win something nice - but just if you complete and submit the questionnaire [1]. And if there are any questions, feedback or you need help don't hesitate a moment to write me an email or ping me on IRC (freenode.net) as unormal. Thanks a lot for your help and tell your fellow KDE mates about this questionnaire [1] Mario Fux >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Keyboard shortcut enhancement.
Am Freitag, 14. Februar 2014 schrieb Andreas Pakulat : > In particular I'm using it to start my preferred browser and to control my preferred mp3 player. The latter is a cli-tool so it has no global shortcuts support but it has invocations which talk to the running instance and can do play, pause etc. > That part of khotkeys has been working for me from KDE 4.2 up until now (4.11 here), so no idea why it is considered to be 'broken'. I think, the only part severely "broken" is triggering random input events. On non non-focused windows that requires xsendevent (for kbd input at least) which noeadays seem largely ignored by clients. This might be different with wayland (ability to discriminate a synthetic event in general?), but i guess it's a security concern.?. An alternative might be a GUI for xbindkeys and a resp. wayland pendant (if such exists), but i guess kglobalaccel would have to be moved to such backend in general. Cheers, Thomas >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
