mirror of
https://github.com/NickeManarin/ScreenToGif.git
synced 2026-04-26 07:35:54 +03:00
[GH-ISSUE #606] Screen size detection is wrong, actural 1920*1080 but show 1919*1079 #499
Labels
No labels
copy cats
duplicated
future feature
pull-request
⬜ Accepted
⬜ Completed
⬜ Help Wanted 💪
⬜ In Progress
⬜ Missing Details
⬜ Pending
⬜ Waiting For Answer ⏳
🆕 feature preview
🔷 Bug 🐛
🔷 Out Of Scope
🔷 Out Of Scope
🔷 Question
🔷Enhancement
🔷Enhancement
🔷Invalid / External
🔷Knowledge Base
🔷Won't Fix
🕑 High
🕑 High
🕑 High
🕕 Medium
🕙 Low
🕛 Critical
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ScreenToGif#499
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 @levid7 on GitHub (Mar 4, 2020).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/606
Originally assigned to: @NickeManarin on GitHub.
My screen is 19201080. However when I use screen mode to select, it show the screen is 19191079. How should I do to capture the full screen 1920*1080? Thanks.
@NickeManarin commented on GitHub (Mar 4, 2020):
Which recorder are you using? The new one?
If so, which selection mode are you using?
If the "region" mode, you can drag 1 pixel to the sides to actually get that one missing pixel.
Or you could simply select the "screen" mode.
@levid7 commented on GitHub (Mar 5, 2020):
I use the new interface and DirectX capture mode. When choosing the screen size, I use the 'screen' mode, but it tells my screen is 1919x1079. Screenshot through PrtSc is attached here, which is 1920x1080.
@NickeManarin commented on GitHub (Mar 5, 2020):
Are you using a high DPI screen?
@levid7 commented on GitHub (Mar 5, 2020):
I don't know whether 1920x1080 is of high DPI. This resolution is my laptop screen resolution, Thinkpad X380 Yoga.
@the-j0k3r commented on GitHub (Mar 5, 2020):
DPI and resolution are separate things.
https://www.tenforums.com/tutorials/5990-change-dpi-scaling-level-displays-windows-10-a.html
Im going to guess that @NickeManarin wants to know if this setting has been changed. Default is 100% or 96DPI (DPI = Dots Per Inch) If you changed it the show us what the settings are now.
@levid7 commented on GitHub (Mar 5, 2020):
O, I got it. Yes I have changed my screen DPI scale, it is 125%. When I change it back to 100%, the screen size indentification is right, 1920x1080.
@NickeManarin commented on GitHub (Mar 5, 2020):
What probably is happening is that the app is receiving the resolution scaled and when converting to 96DPI, it's not rounding correctly the values.
@the-j0k3r commented on GitHub (Mar 5, 2020):
This is predictable, 96DPI = 100% \ 4 = 24DPI increments for each added 25% increase, up to 225% max DPI or 240DPI
That is until some user decides to use this
@levid7 commented on GitHub (May 17, 2020):
Is there any chance to fix this issue?
@NickeManarin commented on GitHub (Jul 1, 2020):
@levid7 I'm working with this right now. I actually redesigning that recorder, to work better with high DPI (and multiple screens) (the other already was update with a better support).
@levid7 commented on GitHub (Jul 6, 2020):
Great and thanks! Waiting for the update.
@SJT1988 commented on GitHub (Jul 22, 2020):
Ditto, same issue, frequently off by one pixel. Not messing with resolution
@NickeManarin commented on GitHub (Aug 8, 2020):
It's done. Since from now on, the recorder will support a multi-DPI set of screens, I'm displaying the actual size and the native size next to it.
If the screen has a scaling of x1.00, only the native size will be displayed.
I'm also working on some optional changes for the recorder UI, you'll be able to check some details about the current selected screen.
@SJT1988 commented on GitHub (Aug 9, 2020):
This is not my reported issue. My reported issue concerned the Cinemagraph
feature.
On Sat, Aug 8, 2020, 2:48 PM Nicke Manarin notifications@github.com wrote:
@NickeManarin commented on GitHub (Aug 9, 2020):
@SJT1988 You received a notification about this issue because you added a comment, 18 days ago.
@levid7 commented on GitHub (Aug 11, 2020):
Great! Waiting for version 2.27.