[GH-ISSUE #73] ScreenToGif UI isn't per-screen DPI aware #1432

New issue

Closed

opened 2026-03-01 18:45:28 +03:00 by kerem · 4 comments

kerem commented 2026-03-01 18:45:28 +03:00

Owner

Copy link

Originally created by @bitcrazed on GitHub (Jan 30, 2017).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/73

Originally assigned to: @NickeManarin on GitHub.

Screen2Gif does not recognize the DPI of the screen on which it is being displayed, and thus renders FAR too big on low-dpi screens (e.g. external 24" screen - top-right) while rendering correctly on high-DPI screen (e.g. my Surface Pro 4's screen - bottom):

External Screens at top, Surface screen below. Surface screen resized to reflect actual physical size)

Machine: Surface Pro 4 (12" @ 2736x1824)
External Screens: 2 x Dell U2412M (24" @ 1920x1200)
OS: Windows 10 Insider Build #15024

Originally created by @bitcrazed on GitHub (Jan 30, 2017). Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/73 Originally assigned to: @NickeManarin on GitHub. Screen2Gif does not recognize the DPI of the screen on which it is being displayed, and thus renders FAR too big on low-dpi screens (e.g. external 24" screen - top-right) while rendering correctly on high-DPI screen (e.g. my Surface Pro 4's screen - bottom): External Screens at top, Surface screen below. Surface screen resized to reflect actual physical size)  Machine: Surface Pro 4 (12" @ 2736x1824) External Screens: 2 x Dell U2412M (24" @ 1920x1200) OS: Windows 10 Insider Build #15024

kerem 2026-03-01 18:45:28 +03:00

• closed this issue
• added the
  🔷 Bug 🐛
  ⬜ Help Wanted 💪
  labels

kerem commented 2026-03-01 18:45:29 +03:00

Author

Owner

Copy link

@NickeManarin commented on GitHub (Jan 31, 2017):

I believe this has something to do with a bug that spoiled recordings with multi-DPI set of screens.

Because the recorder takes into account (while using W8.1 or above) the DPI of the current screen, but the underlying methods that capture the screen does not. Here's an old StackOverflow question.

I could partially solve the bug by making the app unaware of the DPI differences between screens, but I forgot it could turn into a giant window while working with => 150%.

I'm not sure how can I solve this. :/

<!-- gh-comment-id:276233413 --> @NickeManarin commented on GitHub (Jan 31, 2017): I believe this has something to do with a bug that spoiled recordings with multi-DPI set of screens. Because the recorder takes into account (while using W8.1 or above) the DPI of the current screen, but the underlying methods that capture the screen does not. [Here's an old StackOverflow question](http://stackoverflow.com/questions/36818964/dealing-with-multiple-dpi-screens). I could partially solve the bug by making the app unaware of the DPI differences between screens, but I forgot it could turn into a giant window while working with => 150%. I'm not sure how can I solve this. :/

kerem commented 2026-03-01 18:45:29 +03:00

Author

Owner

Copy link

@NickeManarin commented on GitHub (Jan 31, 2017):

You can download version 2.2 (before the fix) to understand what's happening.

<!-- gh-comment-id:276233973 --> @NickeManarin commented on GitHub (Jan 31, 2017): You can [download version 2.2](https://github.com/NickeManarin/ScreenToGif/releases/tag/2.2) (before the fix) to understand what's happening.

kerem commented 2026-03-01 18:45:29 +03:00

Author

Owner

Copy link

@bitcrazed commented on GitHub (Feb 2, 2017):

2.2 looks MUCH better and at least scales vaguely sensibly on my multi-DPI setup ;)

FWIW, the High DPI API docs provide guidance on the different types of DPI support from XP -> 7, 8, 8.1, and now Win10, Win10 Anniversary Update.

One thing we've recently added support for in the Windows Console is better handling of WM_DPICHANGED so that we can select the best fonts & UI elements for the screen the Console is being displayed upon, even if it's dragged around from one screen to the next, or the user changes a display's resolution, orientation, etc.

There are some really great High-DPI improvements coming in Win10 Creators Update too :)

Keep up the great work ;)

<!-- gh-comment-id:276829985 --> @bitcrazed commented on GitHub (Feb 2, 2017): 2.2 looks MUCH better and at least scales vaguely sensibly on my multi-DPI setup ;) FWIW, the [High DPI API docs](https://msdn.microsoft.com/en-us/library/windows/desktop/dd464646%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396) provide guidance on the different types of DPI support from XP -> 7, 8, 8.1, and now Win10, Win10 Anniversary Update. One thing we've recently added support for in the Windows Console is better handling of [WM_DPICHANGED](https://msdn.microsoft.com/en-us/library/windows/desktop/dn312083(v=vs.85).aspx) so that we can select the best fonts & UI elements for the screen the Console is being displayed upon, even if it's dragged around from one screen to the next, or the user changes a display's resolution, orientation, etc. There are some really great [High-DPI improvements coming in Win10 Creators Update](https://blogs.windows.com/buildingapps/2016/10/24/high-dpi-scaling-improvements-for-desktop-applications-and-mixed-mode-dpi-scaling-in-the-windows-10-anniversary-update/#6e8ipgcDuOcY3rpZ.97) too :) Keep up the great work ;)

kerem commented 2026-03-01 18:45:30 +03:00

Author

Owner

Copy link

@NickeManarin commented on GitHub (Feb 2, 2017):

I understand, but v2.2 won't record properly your screen if you drag the recorder to another window with different DPI.

I'll probably have to follow the "Mixed mode" pattern in order to make only the screen recorder window DPI unaware.

<!-- gh-comment-id:277003944 --> @NickeManarin commented on GitHub (Feb 2, 2017): I understand, but v2.2 won't record properly your screen if you drag the recorder to another window with different DPI. I'll probably have to follow the "Mixed mode" pattern in order to make only the screen recorder window DPI unaware.

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

master

dev

v2.40

2.43.1

2.43

2.42.1

2.42

2.41.5

2.41.4

2.41.3

2.41.2

2.41.1

2.41

2.40.1

2.40

2.39

2.38.1

2.38

2.37.2

2.37.1

2.37

2.36

2.35.4

2.35.3

2.35.2

2.35.1

2.35

2.34.1

2.34

2.33.1

2.33

2.32.1

2.32

2.31

2.30.1

2.30

2.29.1

2.29

2.28.2

2.28.1

2.28

2.27.3

2.27.2

2.27.1

2.27

2.26.1

2.26

2.25

2.24.2

2.24.1

2.24

2.23.2

2.23.1

2.23

2.22.1

2.22

2.21.2

2.21.1

2.21

2.20.4

2.20.3

2.20.2

2.20.1

2.20

2.19.3

2.19.2

2.19.1

2.19

2.18

2.17.1

2.17

2.16

2.15.2

2.15.1

2.15

2.14.1

2.14

2.13.3

2.13.2

2.13.1

2.13

2.12.1

2.12

2.11

2.10

2.9

2.8.1

2.8

2.7.3

2.7.2

2.7.1

2.7

2.6

2.5

2.4

2.3.2

2.3.1

2.3

2.2

2.1

Labels

Clear labels   

copy cats

  

duplicated

  

future feature

  

pull-request

Mirrored from GitHub 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 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

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ScreenToGif#1432

No description provided.