On Wednesday 29 May 2024 05:29:53 you wrote:
Anno domini 2024 Wed, 29 May 03:24:44 -0500
J Leslie Turriff via tde-users scripsit:
Pray excuse my ignorance, but what are these XF86* keys you speak of?
The physical keys are the VoumeUP/VolumeDown keys. The XF86Lauch* are used to luanch whatever application you like - in theory.
Nik
So they're the FN keys on a laptop or the "Extra" keys on a Windows keyboard?
Some are, some are not, depends on your keyboard. My desktop cherry-something has 6 "multimediakeys". My X61/T61 have dedicated vol+/-/mute keys. The Rpi400 - for which I needed a solution - has non of these, but the BT connected camera remote has vol+/- for the two shutter keys. So it depends on your hardware what quirky key assignements you have. For now it's a pitty that TDE has some hardwires keyboard funtions, but well, you can't have everything and there are ways around these rough corners :)
Nik
Something that continually irritates me is the way that new features are "introduced" with a new software release. With few exceptions, I discover them AFTER upgrading: openSUSE introduced systemd, dbus, wickd, update-alternatives, PulseAudio, Pipewire, all with no notice to the end-user community; often they were not listed in the Release Notes for the new version, either; and in some cases, e.g. PulseAudio and Pipewire, significant components:
gstreamer-plugin-pipewire pipewire-alsa pipewire-pulseaudio
were not installed, (even though Pipewire is described as "A Multimedia Framework designed to be an audio and video server...", important audio subsystems even pipewire-doc was not installed by default.
In the case of PulseAudio, many subsystems are not even named appropriately by the openSUSE packagers so that they can be associated with PulseAudio:
pavucontrol = PulseAudio Volume Control pavucontrol-qt = Qt port of pavucontrol pavumeter = PulseAudio Volume Meter
who knew to look for them by that name?
It might not be so bad if, in some cases like systemd and wickd, they had not replaced all of the familiar commands with totally new ones generally with non-intuitive names; and don't get me started with Btrfs and snapshotting, which were introduced as defaults with no warning at all, so that many users found their hard drives filled up with snapshots that they didn't realized had been created.
I suppose I am totally spoiled from working in the IBM mainframe environment, where every package (OS and its subsystems, networking, compilers, editors, ...) provided a Migration Guide with its new release...
Leslie