search

Risu / Tiled-Quicklaunch

Plasma Menu Widget for KDE
https://store.kde.org/p/1319588/
GNU General Public License v2.0
3 stars 3 forks source link

Keyboard shortcut does not work #2

Closed psyphre closed 3 years ago

psyphre commented 3 years ago

Love this applet - one of my favs.

Unfortunately the keyboard shortcut does not seem to work. When I set a shortcut and apply, then reopen the settings that shortcut has dissapeared. Using version 3.3.

Let me know what other info you need. Thanks!

Edit: Adding system information:

KDE Plasma 5.19.5 KDE Frameworks: 5.74.0 QT Version 5.14.2

Risu commented 3 years ago

Please provide information about your system, plasma version, framework version and qt version. I cannot reproduce this problem on the KDE Neon User Edition.

psyphre commented 3 years ago

Ok sure, have updated the original post with that information. thanks.

Risu commented 3 years ago

I've tested Kubuntu 20.10 with the same plasma version as yours and keyboard shortcuts are remembered. Maybe you are using the key which is somehow not allowed in plasma?

psyphre commented 3 years ago

Ah, actually i can see what is going on now. The tiled menu that comes up when I click on the mouse is not the same as the tiled menu that comes up when I press the keyboard shortcut. A restart seemed to have fixed the shortcut key not sticking.

The mouse click brings up a menu where I have added tiles to. The keyboard shortcut brings up a blank menu - as if I just added the widget and nothing has yet been added.

I have tried removing the applet and re-adding incase that instance was bugged.

Risu commented 3 years ago

That is different issue for new topic. Quick fix: Insert into risu.tiled.quicklaunch/contents/ui/Main.qml in line 77:

onExpandedChanged: {
    if (expanded && !popup.visible) {
        plasmoid.expanded = false
        popup.visible = true
    }
}

Plasmoids are located in /home/USERNAME/.local/share/plasma/plasmoids. Then restart plasma or system.

psyphre commented 3 years ago

Thanks for the quick responses. I will close this one down and raise a new bug which is specific to this issue,