Hey,
I’m having an issue with the !_NextViewport command. I have it mapped to cmd+W, and it works fine when I make a new file. However, when I use an external monitor and set up the secondary screen with a Floating Viewport, the !_NextViewport command only lets me cycle through two or three views before getting stuck on the Four Viewport view.
Tl;dr: !_NextViewport stops working when I use an extended monitor with a floating viewport
Hi Alex -
I’m seeing something that’s not right but I’m not sure if I’m seeing the same as you do.
At one point I got NextViewport to do nothing at all, but that was after having switched to other applications and then back to Rhino. This is not something that I could reproduce after that one time.
Just to make sure, is this strictly related to using a keyboard shortcut on your end, or does that also happen when you just type NextViewport once and then hit Enter to cycle through viewports?
-wim
Hey Wim,
Thanks for the response. Typing NextViewport and cycling with Enter gets the same result. I made a new file and was able to recreate the issue. I made a screen recording so you can see when the command suddenly stops working after I make a Floating Viewport. I’m also uploading the file.
NextViewportIssue.3dm (4.8 MB)
I guess my real issue is that _NewFloatingViewport is buggy in general? Every time I move from my extended monitor back to my main screen to do something like change a layer, Rhino makes me click the layer twice and often hits the adjacent radio button by mistake.