Tutorials/Keyboard/da: Difference between revisions

From KDE Wiki Sandbox
(Importing a new version from external source)
(Importing a new version from external source)
Line 3: Line 3:
TAstaturhandlinger er alle de handlinger, som udløses af systemet når du trykker på en tast på tastaturet. De fleste af dem skulle være sat op til din tilfredshed som standard. Denne artikel kan hjælpe dig med at lave dine egne indstillinger. De mest oplagte eksempler er funktionerne "forøg lydstyrken" og dens tvilling "formindsk lydstyrken", som findes på nogle multimedie-tastaturer.
TAstaturhandlinger er alle de handlinger, som udløses af systemet når du trykker på en tast på tastaturet. De fleste af dem skulle være sat op til din tilfredshed som standard. Denne artikel kan hjælpe dig med at lave dine egne indstillinger. De mest oplagte eksempler er funktionerne "forøg lydstyrken" og dens tvilling "formindsk lydstyrken", som findes på nogle multimedie-tastaturer.


== Background ==
== Baggrund ==


When a key is pressed, this is sent as an electronic signal over the USB or PS/2 port to the computer. There it is received by the Linux kernel and forwarded to the X Windowing system. The X Windowing system receives the ''scancodes'' of the keys being pressed and maps them to key events, for example XF86audiomute. To change this mapping you have the xmodmap command. To see the scancodes that a keypress causes, you have the xev command. In short, when you press the "Audio Mute" button on your keyboard, the kernel receives the signal from the keyboard and sends a keycode, e.g. 121, to the X Windowing System. Using its xmodmap, the Windowing System emit the signal XF86AudioMute that can be received and handled e.g. by KDE.
When a key is pressed, this is sent as an electronic signal over the USB or PS/2 port to the computer. There it is received by the Linux kernel and forwarded to the X Windowing system. The X Windowing system receives the ''scancodes'' of the keys being pressed and maps them to key events, for example XF86audiomute. To change this mapping you have the xmodmap command. To see the scancodes that a keypress causes, you have the xev command. In short, when you press the "Audio Mute" button on your keyboard, the kernel receives the signal from the keyboard and sends a keycode, e.g. 121, to the X Windowing System. Using its xmodmap, the Windowing System emit the signal XF86AudioMute that can be received and handled e.g. by KDE.

Revision as of 09:44, 20 April 2011

TAstaturhandlinger er alle de handlinger, som udløses af systemet når du trykker på en tast på tastaturet. De fleste af dem skulle være sat op til din tilfredshed som standard. Denne artikel kan hjælpe dig med at lave dine egne indstillinger. De mest oplagte eksempler er funktionerne "forøg lydstyrken" og dens tvilling "formindsk lydstyrken", som findes på nogle multimedie-tastaturer.

Baggrund

When a key is pressed, this is sent as an electronic signal over the USB or PS/2 port to the computer. There it is received by the Linux kernel and forwarded to the X Windowing system. The X Windowing system receives the scancodes of the keys being pressed and maps them to key events, for example XF86audiomute. To change this mapping you have the xmodmap command. To see the scancodes that a keypress causes, you have the xev command. In short, when you press the "Audio Mute" button on your keyboard, the kernel receives the signal from the keyboard and sends a keycode, e.g. 121, to the X Windowing System. Using its xmodmap, the Windowing System emit the signal XF86AudioMute that can be received and handled e.g. by KDE.

Example: The Audio Mute button

If your keyboard's Audio Mute button does not work, you should first find out if it really triggers the correct X Windowing System event. To do this, open a console and enter the command

xev

Move your mouse into the Window that opens. Keep your console in your view and press a key. You will see an output like the following on your console:

 KeyRelease event, serial 35, synthetic NO, window 0x4000001,
     root 0x15a, subw 0x4000002, time 63106815, (43,37), root:(1279,877),
     state 0x10, keycode 121 (keysym 0x1008ff12, XF86AudioMute), same_screen YES,
     XLookupString gives 0 bytes: 
     XFilterEvent returns: False

This means your key triggers the event XF86AudioMute. Fine, then open systemsettings.

Choose Keyboard & Mouse -> Global Keyboard Shortcuts -> KDE Component KMix -> Mute -> Custom. Then click the button and press on the key that you want to use to mute your audio.