Feature request: Privacy screen / Black out client Monitors
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 5.1k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
N/A
**Describe the solution you'd like**
Simply put
An option to Blackout Client Monitors.
Examples:
https://community.teamviewer.com/English/kb/articles/50966-teamviewer-black-screen
**Additional context**
If I'm not mistaken, this is done with a Virtual Display driver. I looked into it and can't seem to wrap my head around it fully yet. If I end up having a eureka moment, ill add it.
Or if anyone can point me in the right direction
Iv added a Connection Banner. still need to finish some things up before I publish.
Also not sure if it's implemented correctly. However, it gets the job done. so ¯\_(ツ)_/¯
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the client monitor and display-handling code, then review how the existing connection banner was added. Done should mean a client-side option reliably blacks out the monitored display while remote control remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100