mirror of
https://github.com/NickeManarin/ScreenToGif.git
synced 2026-04-26 15:46:00 +03:00
[GH-ISSUE #13] Incorrect recording offset and size when Windows font size is above 100% #13
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#13
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 @adbre on GitHub (Sep 21, 2016).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/13
Originally assigned to: @NickeManarin on GitHub.
I have a laptop in a multi-monitor setup. The laptop monitor is configured to 2880x1620. It's placed in a docking station and thus a bit far away as would otherwise be normal if I would have the laptop in my lap, the "size of text, apps and other items" is set to quite high 175%.
The other screen resolutions is 2560x1440 and 1200x1920, both at 100%. Recording on them works fine.
Decreasing the font size on the laptop display to 100% resolves the issue.
Increasing the font size on the other displays reproduces the issue on those displays too.
Update: Using version 2.2
I have attached two screenshots showing this.
@NickeManarin commented on GitHub (Sep 21, 2016):
Thank you for your feedback, this is a known bug.
StackOverflow
I currently have no fix for this bug. :/
@adbre commented on GitHub (Sep 21, 2016):
Even if there's no fix, is the scenario detectable?
I spent a lot of time troubleshooting, when I just wanted to record. Then I discovered it worked if I just dragged what I wanted to record and the recorder to the other screen... A warning/tip would have been extremely helpful at that point.
@NickeManarin commented on GitHub (Sep 23, 2016):
Detecting this kind of issue is hard. It took me some time to understand it too. :/
I had a warning tagged as [Bug] before migrating to GitHub. I'll update the release notes. :)
@NickeManarin commented on GitHub (Oct 11, 2016):
I believe this bug is fixed. Tested with two monitors with different dpi.