TigerVNC/tigervnc

Windows taskbar shows on top of fullscreen vncviewer on secondary monitor

Open

#1,226 opened on Mar 26, 2021

View on GitHub
 (5 comments) (0 reactions) (0 assignees)C++ (1,176 forks)github user discovery
bughelp wanted

Repository metrics

Stars
 (7,396 stars)
PR merge metrics
 (Avg merge 95d 10h) (4 merged PRs in 30d)

Description

Is your feature request related to a problem? Please describe.

I faced the issue with full screen mode on multiple monitor on Windows 10 client.

I have 2 monitors. My taskbar is setup for auto hidden for both monitors. I have notice that Windows has issue with full screen on second monitor.

When I use an app with full screen mode (like Chrome, TigerVNC...) on main monitor, I can hide taskbar completely. Taskbar is not shown when I hover mouse to taskbar area.

However, if I run full screen app on second monitor, whenever I hover mouse to taskbar area, it will be displayed. It is very annoyed when working on remote VNC session.

Describe the solution you'd like There are some games that allow true full screen mode on second monitor without above issue. For example this game.

I want when I click full screen, it will bypass taskbar. Even when I hover mouse to taskbar area, it will not be displayed. I don't know if TigerVNC can implement some functions to fix this issue.

Describe alternatives you've considered There is no alternatives for now.

Additional context N/A

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Contributor guide

Research direction
Investigate Win32 API calls for fullscreen and taskbar behavior on secondary monitors, particularly `SetWindowPos` and `ShowWindow` with proper flags, and consider using `WS EX TOPMOST` or `WS POPUP` style to bypass taskbar. Check existing TigerVNC fullscreen implementation and adapt it for multi monitor.
Tech stack
None
Domain
desktop
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
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.
Mostly clear
Prerequisites
C++Windows API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20