8 Mar
2024
8 Mar
'24
3:53 p.m.
Hi all!
Does anybody know which part of TDE controls XF86RaiseVolume / XF86LowerVolume? I need to
remap these 2 keys to XF86LaunchA / XF86LaunchB but TDE always answers with the OSD volume
bar, even when I remap the beys with xmodmap ...
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
9 Mar
9 Mar
3:09 a.m.
On 2024/03/09 12:53 AM, Dr. Nikolaus Klepp via tde-users wrote:
Hi all!
Does anybody know which part of TDE controls XF86RaiseVolume / XF86LowerVolume? I need to
remap these 2 keys to XF86LaunchA / XF86LaunchB but TDE always answers with the OSD volume
bar, even when I remap the beys with xmodmap ...
Nik
Hi Nik,
tqt3 maps XF86XK_AudioRaiseVolume to TQt::Key_VolumeUp and equivalently for
XF86XK_AudioLowerVolume. Those TQt keys are
then used by KMilo to control the volume up/down and the related OSD visualization.
Hope this helps
Cheers
Michele
8:46 a.m.
H Michele,
Anno domini 2024 Sat, 9 Mar 12:09:47 +0900
Michele Calgaro via tde-users scripsit:
On 2024/03/09 12:53 AM, Dr. Nikolaus Klepp via
tde-users wrote:
Yes, this helps a lot. I did not realizie that kmilo grabs keys before khotkeys sees them.
The workaround would be to uninstall kmilo.
But is there a way to reverse that order, so khotkeys sees and grabs the keys before kmilo
does ?
Nik
Hi all!
Does anybody know which part of TDE controls XF86RaiseVolume / XF86LowerVolume? I need to
remap these 2 keys to XF86LaunchA / XF86LaunchB but TDE always answers with the OSD volume
bar, even when I remap the beys with xmodmap ...
Nik
Hi Nik,
tqt3 maps XF86XK_AudioRaiseVolume to TQt::Key_VolumeUp and equivalently for
XF86XK_AudioLowerVolume. Those TQt keys are
then used by KMilo to control the volume up/down and the related OSD visualization.
Hope this helps Cheers
Michele
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
9:13 a.m.
On 2024/03/09 05:46 PM, Dr. Nikolaus Klepp via tde-users wrote:
Yes, this helps a lot. I did not realizie that kmilo
grabs keys before
khotkeys sees them. The workaround would be to uninstall kmilo.
But is there a way to reverse that order, so khotkeys sees and grabs the
keys before kmilo does ?
That is not entirily correct. Both KMilo and KHotkeys use global accelerators.
Depending on which one run first, the same key could be handle by one or the other. I
played around a bit with the
"lower volume" key and by stop/starting kmilo or by enabling/disabling a khotkey
action, I could get the button to
respond to the first or the second program. What is really needed is a way to change the
hotkeys used by kmilo from the
TDE control panel (I thought this was already possible but I can't seem to find it
anymore).
Cheers
Michele
10:38 a.m.
Anno domini 2024 Sat, 9 Mar 18:13:20 +0900
Michele Calgaro via tde-users scripsit:
On 2024/03/09 05:46 PM, Dr. Nikolaus Klepp via
tde-users wrote:
Interesting. I managed to get XF86LowerVolume be handled by xbindkeys, but not
XF86UpperVolume. I cannot enable/disable kmilo using the TDE control panel. There is a
kmilo checkmark unter "IBM Notebooks", but it is enabled and greyed out.
Nik
Yes, this helps a lot. I did not realizie that
kmilo grabs keys before
khotkeys sees them. The workaround would be to uninstall kmilo.
But is there a way to reverse that order, so khotkeys sees and grabs the
keys before kmilo does ?
That is not entirily correct. Both KMilo and KHotkeys use global accelerators.
Depending on which one run first, the same key could be handle by one or the other. I
played around a bit with the
"lower volume" key and by stop/starting kmilo or by enabling/disabling a
khotkey action, I could get the button to
respond to the first or the second program. What is really needed is a way to change the
hotkeys used by kmilo from the
TDE control panel (I thought this was already possible but I can't seem to find it
anymore).
Cheers
Michele
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
12:38 p.m.
On 2024/03/09 07:38 PM, Dr. Nikolaus Klepp via tde-users wrote:
I cannot enable/disable kmilo using the TDE control
panel. There is a
kmilo checkmark unter "IBM Notebooks", but it is enabled and greyed out.
Hi Nik,
in TCC -> TDE Components -> Service manager, you can enable/disable and start/stop
kmilo in the bottom half of the module.
Cheers
Michele
29 May
29 May
3:42 a.m.
On Friday 08 March 2024 09:53:11 Dr. Nikolaus Klepp via tde-users wrote:
Hi all!
Does anybody know which part of TDE controls XF86RaiseVolume /
XF86LowerVolume? I need to remap these 2 keys to XF86LaunchA / XF86LaunchB
but TDE always answers with the OSD volume bar, even when I remap the beys
with xmodmap ...
Nik
Pray excuse my ignorance, but what are these XF86* keys you speak of?
Leslie
--
Platform: Linux
Distribution: openSUSE Leap 15.5 - x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.1.2
tde-config: 1.0
6:17 a.m.
Anno domini 2024 Tue, 28 May 22:42:38 -0500
J Leslie Turriff via tde-users scripsit:
On Friday 08 March 2024 09:53:11 Dr. Nikolaus Klepp
via tde-users wrote:
The physical keys are the VoumeUP/VolumeDown keys. The XF86Lauch* are used to luanch
whatever application you like - in theory.
Nik
Hi all!
Does anybody know which part of TDE controls XF86RaiseVolume /
XF86LowerVolume? I need to remap these 2 keys to XF86LaunchA / XF86LaunchB
but TDE always answers with the OSD volume bar, even when I remap the beys
with xmodmap ...
Nik
Pray excuse my ignorance, but what are these XF86* keys you speak of?
Leslie
--
Platform: Linux
Distribution: openSUSE Leap 15.5 - x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.1.2
tde-config: 1.0
____________________________________________________
tde-users mailing list -- users(a)trinitydesktop.org
To unsubscribe send an email to users-leave(a)trinitydesktop.org
Web mail archive available at
https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt…
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
8:24 a.m.
On Wednesday 29 May 2024 01:17:19 Dr. Nikolaus Klepp via tde-users wrote:
Anno domini 2024 Tue, 28 May 22:42:38 -0500
J Leslie Turriff via tde-users scripsit:
So they're the FN keys on a laptop or the "Extra" keys on a Windows
keyboard?
Leslie
--
Platform: Linux
Distribution: openSUSE Leap 15.5 - x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.1.2
tde-config: 1.0
On Friday 08 March 2024 09:53:11 Dr. Nikolaus
Klepp via tde-users wrote:
The physical keys are the VoumeUP/VolumeDown keys. The XF86Lauch* are used
to luanch whatever application you like - in theory.
Nik Hi all!
Does anybody know which part of TDE controls XF86RaiseVolume /
XF86LowerVolume? I need to remap these 2 keys to XF86LaunchA /
XF86LaunchB but TDE always answers with the OSD volume bar, even when I
remap the beys with xmodmap ...
Nik
Pray excuse my ignorance, but what are these XF86* keys you speak
of?
10:29 a.m.
Anno domini 2024 Wed, 29 May 03:24:44 -0500
J Leslie Turriff via tde-users scripsit:
On Wednesday 29 May 2024 01:17:19 Dr. Nikolaus Klepp
via tde-users wrote:
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
Anno domini 2024 Tue, 28 May 22:42:38 -0500
J Leslie Turriff via tde-users scripsit:
So they're the FN keys on a laptop or the "Extra" keys on a Windows
keyboard? On Friday 08 March 2024 09:53:11 Dr. Nikolaus
Klepp via tde-users wrote:
The physical keys are the VoumeUP/VolumeDown keys. The XF86Lauch* are used
to luanch whatever application you like - in theory.
Nik Hi all!
Does anybody know which part of TDE controls XF86RaiseVolume /
XF86LowerVolume? I need to remap these 2 keys to XF86LaunchA /
XF86LaunchB but TDE always answers with the OSD volume bar, even when I
remap the beys with xmodmap ...
Nik
Pray excuse my ignorance, but what are these XF86* keys you speak
of?
Leslie
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
11:30 p.m.
New subject: New distro features poorly introduced (was Who controls XF86RaiseVolume / XF86LowerVolume?)
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:
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
--
Platform: Linux
Distribution: openSUSE Leap 15.5 - x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.1.2
tde-config: 1.0
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
30 May
30 May
6:36 a.m.
New subject: New distro features poorly introduced (was Who controls XF86RaiseVolume / XF86LowerVolume?)
Anno domini 2024 Wed, 29 May 18:30:43 -0500
J Leslie Turriff via tde-users scripsit:
On Wednesday 29 May 2024 05:29:53 you wrote:
[...]
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...
You might want to peek at FreeBSD.
Nik
Leslie
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
205
days inactive
288
days old
11 comments
3 participants
participants (3)
-
Dr. Nikolaus Klepp -
J Leslie Turriff -
Michele Calgaro