Forum > Editor

IDE: Keys which do not work in the Default key mapping on Qt6.

(1/3) > >>

dsiders:
I recently started using Lazarus on a Linux platform with KDE Plasma 6.


* Lazarus 3.99 (rev main_3_99-2093-g82cc65e98b)
* FPC 3.2.2
* x86_64-linux-qt6
* AnchorDocking and DockedFormEditor installed

* Operating System: openSUSE Tumbleweed 20240607
* KDE Plasma Version: 6.0.5
* KDE Frameworks Version: 6.2.0
* Qt Version: 6.7.1
* Graphics Platform: X11
I found that the following keys, mapped as the "KeyA" settings in the default key mapping, do not do anything:


* Ctrl + / = Toggle Comment
* Alt + D = Cut current line
* Ctrl + E = Find Incremental (TBH I don't know what this is supposed to do...)
* Ctrl + Shift + M = Insert from Character Map
* Ctrl + Shift + <#> = Toggle marker number # (Ctrl + K + <#> works though)
Are these known issues on Linux? Or the Qt6 widgetset? Or, it is worthy of a bug report?

Feedback appreciated.

zeljko:
Please fill issue with example project.

TRon:
Would it not be more productive to extend issue 40952 ? (I honestly do not know what is the best route there)

MarkMLl:
I'm uncomfortable here, but I'd suggest that this is something we have to live with and that it's largely a documentation issue.

I'm an habitual KDE user, but for the last few years have used a gamer's keypad to beat the IDE into panting submission.

There are, quite simply, some key combinations ** which don't work since they've been preempted at a lower level, and about the best that we can do is point users at (a) a way of determining that the window manager (etc.) has claimed them and (b) a way to tell the IDE to use something different.

MarkMLl

** As one of the older members of the community, I have strong views on this. Due to inevitable wear and tear, I find the physical (and mental) contortions needed to invoke IDE shortcuts to be between uncomfortable and impossible.

I have seen things... I have seen a word processor keyboard designed by a woman for lady typists which had so many key combinations that it put Emacs to shame https://ichef.bbci.co.uk/news/976/cpsprodpb/17C23/production/_104751379_9c0bd761-972a-4627-b74e-fb42307e4466.jpg.webp

If a potential operation can't be presented as a selection on a top-of window/screen or dropdown menu, together with a succinct explanation of what it will do, then something (probably the IDE developer) is badly broken.

I am not denying that keyboard shortcuts can be useful. But when a user is switching between substantially different application areas- text processing to 2D drafting to 3D design- there are so many conceptual possibilities that trying to remember key combinations for them becomes infeasible.

Larry Tesler's rallying cry was "Don't mode me in", but quite frankly history has proven him wrong. If one is working in a word processor or a 2D drawing program, should 3D operations be presented as a distraction?

I'm not known for praising MS, but they built the Windows '95 ("Chicago") user interface on top of CUA, and broadly speaking they got it right. At any given time there's probably a half-dozen keyboard shortcuts that the average user can keep in his memory, and if he can't retain those then they (and other significant operations) should be readily accessible via menus.

dsiders:

--- Quote from: zeljko on June 08, 2024, 09:50:18 pm ---Please fill issue with example project.

--- End quote ---

I should have been more specific. The context for the errors (omissions) is the Lazarus IDE.

I can write an app to catch those keystrokes though. I'll file a bug report when I complete the demo.

Navigation

[0] Message Index

[#] Next page

Go to full version