[GH-ISSUE #164] The new recorder UI does not support multi-screen #1507

Closed
opened 2026-03-01 18:46:06 +03:00 by kerem · 9 comments
Owner

Originally created by @walterlv on GitHub (Jul 18, 2017).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/164

Originally assigned to: @walterlv, @NickeManarin on GitHub.

When the new recorder UI is enabled (just as the setting item below) , I find that it does not support multi-screen.
the new recorder ui

In details:

  • When the editor UI shows in the extended screen, the new recorder UI will no longer show any pixel.
  • But even when the editor UI shows on the main screen, the new recorder UI still show half when it is dragged to the edge.
    imageimage
    (Normal on the left and clipped on the right)
  • When Area is activated, the Area selection window only shows on the main screen. Then I can't record on the extended screen.
Originally created by @walterlv on GitHub (Jul 18, 2017). Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/164 Originally assigned to: @walterlv, @NickeManarin on GitHub. When the new recorder UI is enabled (just as the setting item below) , I find that it does not support multi-screen. ![the new recorder ui](https://user-images.githubusercontent.com/9959623/28295859-9389dac2-6b96-11e7-9e94-b6059a4c865f.png) In details: - When the editor UI shows in the extended screen, the new recorder UI will no longer show any pixel. - But even when the editor UI shows on the main screen, the new recorder UI still show half when it is dragged to the edge. ![image](https://user-images.githubusercontent.com/9959623/28295954-70ee2b84-6b97-11e7-8fd9-edd3d97b993a.png)![image](https://user-images.githubusercontent.com/9959623/28296001-bbfde5ba-6b97-11e7-80eb-1bc5b0b559fb.png) (Normal on the left and clipped on the right) - When `Area` is activated, the `Area selection` window only shows on the main screen. Then I can't record on the extended screen.
kerem 2026-03-01 18:46:06 +03:00
Author
Owner

@NickeManarin commented on GitHub (Jul 18, 2017):

I need a few details about this bug:

Are you using a high DPI monitor?
Did you connect the external/second monitor after opening the recorder?

<!-- gh-comment-id:316224058 --> @NickeManarin commented on GitHub (Jul 18, 2017): I need a few details about this bug: Are you using a high DPI monitor? Did you connect the external/second monitor after opening the recorder?
Author
Owner

@walterlv commented on GitHub (Jul 20, 2017):

I have two monitors connecting to my PC.

  • Both use 96Dpi.
  • Neither of them connect or disconnect during the Recorder Window displaying.
  • I can reproduce this issue everytime with normal procedure.

To solve this issue, we could not create a maximized window and put a recorder UI onto it. These may help:

  • Use multi-window and display each of them in one screen.
  • Use a single window with non-maximized state and cover it to all screens.

Maybe I can find out and solve this issue this weekend. After that, I will create a new pull request.

EDIT

I realize that you've done all the efforts above, but it still happens.

<!-- gh-comment-id:316628210 --> @walterlv commented on GitHub (Jul 20, 2017): I have two monitors connecting to my PC. - Both use 96Dpi. - Neither of them connect or disconnect during the Recorder Window displaying. - I can reproduce this issue everytime with normal procedure. --- To solve this issue, we could not create a maximized window and put a recorder UI onto it. These may help: - Use multi-window and display each of them in one screen. - Use a single window with non-maximized state and cover it to all screens. Maybe I can find out and solve this issue this weekend. After that, I will create a new pull request. ### EDIT I realize that you've done all the efforts above, but it still happens.
Author
Owner

@NickeManarin commented on GitHub (Jul 22, 2017):

Oh, I think that I understand what's happening.

Is your secondary screen to the left of your primary screen?

<!-- gh-comment-id:317144184 --> @NickeManarin commented on GitHub (Jul 22, 2017): Oh, I think that I understand what's happening. Is your secondary screen to the left of your primary screen?
Author
Owner

@NickeManarin commented on GitHub (Jul 22, 2017):

I just tested in here... I was assuming that no monitor would use a negative position (> 0;0/Left;Top), but if the secondary display is set to the left side, the app won't cover that screen.

image

<!-- gh-comment-id:317144323 --> @NickeManarin commented on GitHub (Jul 22, 2017): I just tested in here... I was assuming that no monitor would use a negative position (> 0;0/Left;Top), but if the secondary display is set to the left side, the app won't cover that screen. ![image](https://user-images.githubusercontent.com/14798947/28487207-83a40f28-6e62-11e7-81aa-25ec24d633fb.png)
Author
Owner

@NickeManarin commented on GitHub (Jul 22, 2017):

To solve this, it's pretty simple, just set Left and Top to the VirtualScreen coordinates:

image

Of course, there's a few adjustments to make, but nothing big.

<!-- gh-comment-id:317144509 --> @NickeManarin commented on GitHub (Jul 22, 2017): To solve this, it's pretty simple, just set Left and Top to the VirtualScreen coordinates: ![image](https://user-images.githubusercontent.com/14798947/28487216-e904f2c4-6e62-11e7-9ffd-5ac66e0b46f7.png) Of course, there's a few adjustments to make, but nothing big.
Author
Owner

@walterlv commented on GitHub (Jul 22, 2017):

You'are right!
My secondary screen is on the left.

<!-- gh-comment-id:317144582 --> @walterlv commented on GitHub (Jul 22, 2017): You'are right! My secondary screen is on the left.
Author
Owner

@walterlv commented on GitHub (Jul 22, 2017):

It's not that simple.
It is possible that your coordinate will be incorrect when your window location changes.

<!-- gh-comment-id:317144800 --> @walterlv commented on GitHub (Jul 22, 2017): It's not that simple. It is possible that your coordinate will be incorrect when your window location changes.
Author
Owner

@NickeManarin commented on GitHub (Jul 22, 2017):

When the window location changes, it's possible to detect the new arrangement by listening to this event:

SystemEvents.DisplaySettingsChanged += (sender, args) => { Dialog.Ok("a", "b", "c"); };

<!-- gh-comment-id:317145084 --> @NickeManarin commented on GitHub (Jul 22, 2017): When the window location changes, it's possible to detect the new arrangement by listening to this event: `SystemEvents.DisplaySettingsChanged += (sender, args) => { Dialog.Ok("a", "b", "c"); };`
Author
Owner

@walterlv commented on GitHub (Jul 24, 2017):

Solved. See #166 .

<!-- gh-comment-id:317306031 --> @walterlv commented on GitHub (Jul 24, 2017): Solved. See #166 .
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
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#1507
No description provided.