mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Notification area icon double-click-ability #4784
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#4784
Loading…
Add table
Add a link
Reference in a new issue
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?
Originally created by @mica on GitHub (Oct 13, 2016).
I would be nice if double-clicking on the Windows notification area icon would open the app, rather than just quickly open then close it.
You could keep the usual single-click-to-open behaviour, but just ignore the second click if it occurs within a few hundred milliseconds of the first.
This throws me off almost every time I go to open qBittorrent. It's probably the only app I've encountered that behaves this way.
@thalieht commented on GitHub (Oct 14, 2016):
Faulty mouse? What's wrong with single click?
@mica commented on GitHub (Oct 14, 2016):
Point is, either a single-click or a double-click should open the app. As is, double-click does nothing (or opens/closes so quickly as to effectively do nothing), which is contrary to expected behavior, and every app I've encountered.
And no, nothing wrong with the mouse. Just the behavior of the app. Give it a try.
@ngosang commented on GitHub (Jan 14, 2017):
@Chocobo1 seems easy ;)
@Chocobo1 commented on GitHub (May 2, 2017):
See PR #6730.