V8 GH script editor window invisible and misplaced

This is driving me nuts today… Even after restarting Rhino, I am finding that when double clicking on a script editor component to edit it, that it is invisible.

Here I have two open and one is showing far away from where it is supposed to be, and the other is not findable at all. I have two monitors, but it’s not on the other monitor either.

Given the displacement to the right of the one that is visible (between where it is and “where it should be”), I assume that Rhino thinks the other one is actually off the screen somewhere even further to the right. I don’t see any way to reset it.

This also happens when I only have one script editor component on the canvas, so having two is not the problem.

Edit:
Confirmed… I closed Rhino, re-opened it and pushed the main Rhino window onto the left monitor (previously it was on the right). I then opened GH (same file as before) and double clicked on the script component. The editor window showed up way off to the right on the second (right) monitor).

So it is clear that previously Rhino thought the editor window was off-screen somewhere to the right of my rightmost monitor. Something is wonky with the management of these window positions…

Pushed the editor window back onto the right monitor as well. The indication of where the editor window “should be” is still way off - the actual window is much further to the right and below.

Closed GH and Rhino, opened it again on the right monitor and attempted to open both script components. Now I have both editor windows visible, but the indication of where they should be (way off to the left) is completely nuts…

Uh this is ugly. I will fix it for tomorrow’s 8.6 - Do you have a high dpi monitor with higher than 100% scaling?

RH-81318 Editor window ends up out of monitor bounds

Yep, 2x 4K monitors @ 150%…

1 Like

RH-81318 is fixed in Rhino 8 Service Release 6

2 Likes

Finally. Thank you guys!

1 Like

@martinsiegrist 8.7 RC should be even better :smiley:

1 Like

@martinsiegrist This issue also happened and I put a fix for the next 8.7 RC