@ -41,11 +41,11 @@ to hide it use "hide" instead of show and if you are lazy you can just use "togg
DCOP Calls are most useful, if you try to invoke Kommando through an external application, that is only able to start execute console commands.
DCOP Calls are most useful, if you try to invoke Kommando through an external application, that is only able to start execute console commands.
KNOWN ISSUES/ PLANNED FEATURES:
KNOWN ISSUES/ PLANNED FEATURES:
- Kommando does not respect the screen border and kicker, so if you invoke it close to one of both, some buttons will be obscured (on my KDE 3.5 box this problem does not exist anymore, but there are some graphics artifacts in the background image)
- Kommando does not respect the screen border and kicker, so if you invoke it close to one of both, some buttons will be obscured (on my TDE 3.5 box this problem does not exist anymore, but there are some graphics artifacts in the background image)
A final statement?
A final statement?
Yes, if you have any suggestions/enhancements/criticism or found a nasty bug please let me know!
Yes, if you have any suggestions/enhancements/criticism or found a nasty bug please let me know!
A wheelmenu for KDE powerusers which pops up and gives easy access to start some favorite programs with the mouse.
A wheelmenu for TDE powerusers which pops up and gives easy access to start some favorite programs with the mouse.
.br
.br
Kommando is configured by a xml-based file format in ~/.kde/share/apps/kommando/kommandorc which can be edited manually or through kommando configuration interface. If no kommandorc-file is found, the configuration interface will appear on program start. In kommando 0.3 the configuration file was ~/.kommandorc
Kommando is configured by a xml-based file format in ~/.kde/share/apps/kommando/kommandorc which can be edited manually or through kommando configuration interface. If no kommandorc-file is found, the configuration interface will appear on program start. In kommando 0.3 the configuration file was ~/.kommandorc