hluk/CopyQ

MacOS CopyQ Main Window Jumps to Primary Screen When Triggered via Hotkey in Fullscreen Mode

Open

#2,902 opened on Nov 17, 2024

View on GitHub
 (3 comments) (1 reaction) (0 assignees)C++ (419 forks)batch import
bughelp wantedmacOS

Repository metrics

Stars
 (7,372 stars)
PR merge metrics
 (Avg merge 17h 35m) (13 merged PRs in 30d)

Description

Describe the bug

On macOS 15.1, when a fullscreen application is active, using the configured hotkey to bring up the CopyQ main window causes the window to jump back to the primary screen. This prevents the CopyQ main window from appearing within the fullscreen application.

To Reproduce

1.	Install and run CopyQ on macOS 15.1.
2.	Configure a global hotkey to show the CopyQ main window.
3.	Open any application that supports fullscreen mode (e.g., Safari or VSCode) and switch it to fullscreen.
4.	While the fullscreen application is active, press the configured hotkey to open the CopyQ main window.

Expected behavior

Pressing the hotkey should bring up the CopyQ main window on the current screen, even when a fullscreen application is active, without switching back to the primary screen.

Screenshots none

Version, OS and Environment

  • Operating System: macOS 15.1
  • CopyQ Version: 9.1.0-g4aab2525-v9.1.0
  • Hardware: apple m4

Additional context

This issue only occurs in fullscreen mode. The hotkey functions normally when not in fullscreen mode.

Contributor guide

Research direction
Investigate how CopyQ handles window placement when triggered by hotkey on macOS, especially in fullscreen spaces. Look at the code that sets window position and screen assignment, and consider using macOS APIs like NSScreen or NSWindow to ensure the window appears on the active screen.
Tech stack
cpp
Domain
desktop
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++QtmacOS development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70