Bitmessage/PyBitmessage-2025-02-20
Archived
2
0
Fork 0
Code Issues 167 Pull Requests 54 Actions Packages Projects Releases 5 Wiki Activity

Keyboard shortcut issues #284

New Issue
Open
opened 2013-07-04 03:32:59 +02:00 by Dokument · 2 comments
Dokument commented 2013-07-04 03:32:59 +02:00 (Migrated from github.com)
Copy Link

I was contacted about an issue regarding keyboard navigation in bitmessage. I could not replicate the Ctrl+Tab issue in my .exe compiled version but perhaps someone else could.

"But regarding the keyboard behavior, try to reproduce the problem by these
steps:

Start the client.
Press Ctrl+Tab, and you are in the
main window.

Pressing Ctrl+Tab brings up respectively Inbox, Send, Sent, Your Identities,
Subscriptions, Addressbook, Blacklist, Network Status.

Pressing Ctrl+Tab moves to the next and Ctrl+Shift+Tab to the previous
window.

So far so good, but press tab once more for example to bring up the Inbox.

Ctrl+tab does not bring up the next window (Send) while you are stuck inside
the Inbox or any other menu.

Only the mouse does.
Regardless where you are, Ctrl+Tab and Ctrl+Shift+Tab should always bring up
the next and previous menu.

So if you are in the Inbox pressing Ctrl+Tab should bring up Send, Your
Identities etc.

I would also like to have keyboard shortcuts for bringing up Settings and
exiting the program.

This would also be useful for people depending on the keyboard for other
reasons - like accessibility aids."

I was contacted about an issue regarding keyboard navigation in bitmessage. I could not replicate the Ctrl+Tab issue in my .exe compiled version but perhaps someone else could. "But regarding the keyboard behavior, try to reproduce the problem by these steps: Start the client. Press Ctrl+Tab, and you are in the main window. Pressing Ctrl+Tab brings up respectively Inbox, Send, Sent, Your Identities, Subscriptions, Addressbook, Blacklist, Network Status. Pressing Ctrl+Tab moves to the next and Ctrl+Shift+Tab to the previous window. So far so good, but press tab once more for example to bring up the Inbox. Ctrl+tab does not bring up the next window (Send) while you are stuck inside the Inbox or any other menu. Only the mouse does. Regardless where you are, Ctrl+Tab and Ctrl+Shift+Tab should always bring up the next and previous menu. So if you are in the Inbox pressing Ctrl+Tab should bring up Send, Your Identities etc. I would also like to have keyboard shortcuts for bringing up Settings and exiting the program. This would also be useful for people depending on the keyboard for other reasons - like accessibility aids."
PeterSurda commented 2015-10-18 11:32:13 +02:00 (Migrated from github.com)
Copy Link

The new UI has different elements, however, similar problems exist.

The new UI has different elements, however, similar problems exist.
PeterSurda commented 2016-04-28 15:36:51 +02:00 (Migrated from github.com)
Copy Link

I can reproduce similar behaviour on the mailchuck fork. I think this should be standardised.

I can reproduce similar behaviour on the mailchuck fork. I think this should be standardised.
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working as it's supposed to
build
Related to building or build system
dependencies
Pull requests that update a dependency file
developers
The issue is relevant mainly for developers rather than users
documentation
duplicate
enhancement
New feature
formatting
Code or UI text formatting
invalid
legal
mobile
Frontend for mobile devices (kivy)
obsolete
packaging
performance
protocol
Protocol change
question
refactoring
regression
Some issue, fixed in the past, appears again
security
test
translation
usability
wontfix
No Label
enhancement
Milestone
No items
No Milestone v0.8.0
Projects
Clear projects
No project
Assignees
Clear assignees
PeterSurda
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Bitmessage/PyBitmessage-2025-02-20#284
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?