高分辨率截图组件无法全屏截图，只能识别成分辨率/缩放倍数
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
Research direction
Start with the screenshot component used by the demonstration program and reproduce the issue on .NET Framework 4.0. Check how the display size and scaling factor limit the capture area; done means a high-resolution display can be captured across its full screen rather than stopping at 1440×900.
Written by the indexing model from the issue text.
Description
Describe the bug
比如我这个分辨率识别出来就是1440*900，最大截图范围就是这个范围内的。
Steps to reproduce the bug
我是用的演示程序测试的
Expected behavior
No response
Screenshots
No response
NuGet package version
None
IDE
No response
Framework type
.Net Framework 4.0.0
Windows version
No response
Additional context
No response
- Dominant language
- C#
- Stars
- 7.2k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from HandyOrg/HandyControl
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
HandyOrg/HandyControl#1818 · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
HandyOrg/HandyControl#1809 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
HandyOrg/HandyControl#1820 ·
-
不能够独立的引入用户认为需要的部分Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
HandyOrg/HandyControl#1816 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
HandyOrg/HandyControl#1813 ·
All issues in HandyOrg/HandyControl
Similar issues
-
:watch: Not Triaged dotnet-target-version
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
copilot documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 2 days
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
dotnet/dotnet-api-docs#13124 ·
Maintainers usually reply within 1 day
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
BHoM/MidasCivil_Toolkit#441 ·