[SOLVED] Interval double click mouse

thommen · 2018-08-30 09:20:36

I have KDE, but I not have advance settings mouse. I want to set interval double click. I not install xinput. I use it Xorg.

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 340.107  (buildmeister@swio-display-x64-rhel04-13)  Thu May 24 22:29:46 PDT 2018

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 340.107  (buildmeister@swio-display-x64-rhel04-13)  Thu May 24 22:29:58 PDT 2018

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 1680 0
    Screen      1  "Screen1" 0 0
    Screen      2  "Screen2" 3360 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "1"
EndSection

Section "Files"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Philips 200WB"
    HorizSync       30.0 - 98.0
    VertRefresh     56.0 - 76.0
    Option         "DPMS"
EndSection

Section "Monitor"
    Identifier     "Monitor1"
    VendorName     "Unknown"
    ModelName      "Philips 200WB"
    HorizSync       30.0 - 98.0
    VertRefresh     56.0 - 76.0
EndSection

Section "Monitor"
    Identifier     "Monitor2"
    VendorName     "Unknown"
    ModelName      "Philips 200WB"
    HorizSync       30.0 - 98.0
    VertRefresh     56.0 - 76.0
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "NVS 300"
    BusID          "PCI:3:0:0"
EndSection

Section "Device"
    Identifier     "Device1"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "NVS 300"
    BusID          "PCI:4:0:0"
EndSection

Section "Device"
    Identifier     "Device2"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "NVS 300"
    BusID          "PCI:5:0:0"
EndSection

Section "Screen"

# Removed Option "metamodes" "DP-0: nvidia-auto-select +0+0, DP-1: nvidia-auto-select +1680+0"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "CRT-0"
    Option         "metamodes" "DP-0: nvidia-auto-select +0+0, DP-1: nvidia-auto-select +0+1050"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"

# Removed Option "metamodes" "DP-0: nvidia-auto-select +0+0, DP-1: nvidia-auto-select +1680+0"
    Identifier     "Screen1"
    Device         "Device1"
    Monitor        "Monitor1"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "CRT-0"
    Option         "metamodes" "DP-0: nvidia-auto-select +0+0, DP-1: nvidia-auto-select +0+1050"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"

# Removed Option "metamodes" "DP-0: nvidia-auto-select +0+0, DP-1: nvidia-auto-select +1680+0"
    Identifier     "Screen2"
    Device         "Device2"
    Monitor        "Monitor2"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "CRT-0"
    Option         "metamodes" "DP-0: nvidia-auto-select +0+0, DP-1: nvidia-auto-select +0+1050"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Last edited by thommen (2018-08-30 14:51:40)

seth · 2018-08-30 11:27:11

"kcmshell5 mouse", the double click interval is a client side thing and not related to the X11 server. The KDE settings should affect at least all Qt clients, the doubleclick interval in other clients is subject to other config items (if such exist)

thommen · 2018-08-30 11:51:16

In KDE, now I have → https://image.ibb.co/kthtmU/cRzWcyz.png, I am looking for a solution to get → https://image.ibb.co/dvAURU/GUvqCjs.png. I am looking for a different solution, without KDE.

seth · 2018-08-30 12:14:43

If you're using KDE and thus the KDE platform plugin, there is no "different solution, without KDE". It's a 100% client thing, the concept of a doubleclick does not exist in X11.
If some wacko at the VDG decided to go full gnome and scratch that config in favor of a hardcoded value, you're simply screwed.

The mouse kcm is part of plasma-desktop, if the first screenshot shows a new "kcmshell5 mouse", complain at KDE or use a different environment.

thommen · 2018-08-30 12:34:59

Thank you for your help. I understood.

Last edited by thommen (2018-08-30 12:35:08)

seth · 2018-08-30 13:58:26

If you're willing to ditch the KDE platform plugin, you can use Qt5ct, https://wiki.archlinux.org/index.php/Qt … KDE_Plasma (obviously adapt the export script), but it gives me pause that KDE has really removed this setting??
Your screenshot is according to google the kcm for some "pointing device", not the mouse - there should be more kcms in that systemsettings page and notably if you launch them by kcmshell.
Also the autogenerated (no idea how up-to-date, though) KDE docs clearly indicate that the setting is still there.
Did you run "kcmshell5 mouse"?

thommen · 2018-08-30 14:19:20

This is a screenshot of my system after issuing the command "kcmshell5 mouse" → https://image.ibb.co/cFiGv9/Screenshot_ … 160912.png
I found a topic → https://forum.kde.org/viewtopic.php?f=289&t=152982. I not installed "xorg-xinput"
I opened the topic → https://forum.kde.org/viewtopic.php?f=289&t=153755

Last edited by thommen (2018-08-30 14:21:46)

seth · 2018-08-30 14:27:12

You cannot control this w/ xinput (unlike the acceleration that the thread talks about)
Apparently the knuckleheads that now run KDE really screwed up - sorry :-(

You can try to edit the value in ~/.config/kdeglobals, [KDE] section, "DoubleClickInterval=<ms>"
No idea whether that's still a parsed value, though.

thommen · 2018-08-30 14:51:20

seth wrote:

You cannot control this w/ xinput (unlike the acceleration that the thread talks about)
Apparently the knuckleheads that now run KDE really screwed up - sorry :-(

This is a screenshot of my brother system after issuing the command "kcmshell5 mouse" (Manjaro KDE) → https://image.ibb.co/fQpWCp/photo_2018_ … _32_52.jpg

seth wrote:

You can try to edit the value in ~/.config/kdeglobals, [KDE] section, "DoubleClickInterval=<ms>"

This is the solution. Thank you for your time and help

V1del · 2018-08-30 14:55:11

IIRC you can get the old dialog back by switching the xorg backend to xf86-input-evdev though I haven't tried that myself yet and they might have removed that fallback in the meantime as well.

Arch Linux

#1 2018-08-30 09:20:36

[SOLVED] Interval double click mouse

#2 2018-08-30 11:27:11

Re: [SOLVED] Interval double click mouse

#3 2018-08-30 11:51:16

Re: [SOLVED] Interval double click mouse

#4 2018-08-30 12:14:43

Re: [SOLVED] Interval double click mouse

#5 2018-08-30 12:34:59

Re: [SOLVED] Interval double click mouse

#6 2018-08-30 13:58:26

Re: [SOLVED] Interval double click mouse

#7 2018-08-30 14:19:20

Re: [SOLVED] Interval double click mouse

#8 2018-08-30 14:27:12

Re: [SOLVED] Interval double click mouse

#9 2018-08-30 14:51:20

Re: [SOLVED] Interval double click mouse

#10 2018-08-30 14:55:11

Re: [SOLVED] Interval double click mouse

Board footer