Community-edition: Rambox appears Offscreen if Monitor configuration is changed while Rambox is closed

[DWSR]

Steps to reproduce

1. Connect computer to multiple monitors.
2. Place Rambox on a secondary monitor (i.e. not the laptop panel)
3. Shutdown the computer (and Rambox)
4. Connect the computer to another set of monitors in a different configuration
5. Start Rambox

Expected behavior

Rambox appears on the default (primary) monitor

Actual behavior

Rambox appears offscreen and requires keyboard shortcuts to move back into the visible viewport

ENVIRONMENT

OS: Windows 10 Enterprise 1703 Build 16199
Rambox: 0.5.9
Arch: x64

[nmat]

Hello, I believe this could be a electron issue. I have the same type of effect from atom. Can you test to use atom also to see if the display problems happens there also?

[nmat]

I have checked the electron issues a bit and seems like this one here is related: https://github.com/electron/electron/issues/4045 or I might be wrong

[DWSR]

Hi @nmat,

I'm using VSCode (also Electron based) and haven't had this issue. Perhaps they have some code that handles this case?

[nmat]

They could be using a different version of electron also. AFAIK this occurs on windows 10 mostly because of calculations. I have had similar issues with for example slack etc. So not 100% certain it is actually a issue with rambox itself.

[DWSR]

I'm not having an issue with the UWP Slack app, nor any of the several Electron based MSFT application that I run. Either they have specific code for this problem (possible) or there is a problem with the way that Rambox calculates window position.

Related #323

[Bruce17]

I had the same problem on my Win10 machine and I was not able to move the window at all. Close Rambox, open its config file (windows: C:\Users\mir\AppData\Roaming\Rambox\config.json) and alter the attribute x: ... to a positive value. I altered it to x: 0. Now my window is in view again. I don't know how this happened, but it is really annoying.

[driehle]

Thanks @Bruce17 for the hint to the config.json. Worked well for me! All the mentioned screenshots do not work when you are using a remote desktop connection, so editing the config.json seems to be the only soulution then.

[DWSR]

You can also Shift+Right click the application on the SuperBar and select Move. Then, tap an arrow key a couple of times, then move your mouse. The window should come back into focus.

[Bruce17]

@DWSR This was the first thing I tried, but it didn't work either in my case.

[Casyi]

Nothing worked, except @Bruce17 config.json solution. Thank you.

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.