Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Window opens on wrong (disconnected) monitor

See original GitHub issue

Bug report

I understand the difference between Streamlink and Streamlink Twitch GUI.
This is a bug report and I have read the contribution guidelines.

Environment details

Operating system and version:
Windows 10 Pro 1903

Streamlink Twitch GUI version:
v1.8.1

Description

I normally run a dual monitor setup (one on the laptop, the other one external). Usually the external one is set as my primary in Windows.

I am now only using the laptop, without the external monitor attached. Windows is set to “PC screen only” (Win+P), and Windows is aware that only one (the internal one) is there. I also rebooted Windows with no monitor attached.

When I open streamlink-twitch-gui, “nothing” appears. But if I hover over the task bar, I can see that it did indeed open and it looks like it’s open on the (non-existent) external monitor (i.e. if I hover over the icon, the preview of the open GUI appears in the task bar).

Sometimes, with other apps, what one can do is click the icon (so that the app window is in focus), and then press Win+ArrowKeyRight (or Left), to move around the “invisible” window between screens and make it appear on the “main” screen. However this did not work here.

Expected / Actual behavior

If only one monitor is there, streamlink-twitch-gui should appear on the monitor, and not “hidden” on a non-existent monitor.

Reproduction steps

See above.

Log output

I was able to “fix” it and make it appear on the main screen with streamlink-twitch-gui.exe --reset-window. So, feel free to close this, but I thought you might be interested in the bug report.

Issue Analytics

State:
Created 4 years ago
Comments:6 (2 by maintainers)

Top GitHub Comments

2reactions

bastimeyercommented, Dec 30, 2019

This is a bit surprising. Before Streamlink Twitch GUI’s window becomes visible, it first performs an out-of-bounds detection, and it also does this each time the screen configuration changes while the app is running. This all relies on the screen interface which NW.js provides, but since it has to be tested with a stubbed interface, it’s possible that something changed over the past NW.js release upgrades and broke the current implementation.

I’ll take a look at it when I get the time. I’ll also see if I can add some debug log messages to the initializer, so users can understand what’s going on without having to use a development build.