Error in rs.PopupMenu() location

Scripting
,
1

Does anyone have a workaround for rs.PopupMenu() popping up in the wrong position? By default it is supposed to popup under the cursor, but since V7 or earlier it always is way far away for me, most often in the lower right hand corner of the screen.

I have posted about this a long time ago, but nothing has been done. It may be that this phenomenon is due to display scaling? I just now tried to figure out how to get the cursor position and calculate myself in screen coordinates to feed to the method, but I failed miserably - I’m not very good with this stuff.

Has anyone ever tried to program a workaround?

2

Partially (and hopefully correctly) answering my own question - the answer to it might be yes.

I tried scaling the X and Y coordinates of the cursor location according to the display scaling I have here - 225%:

import rhinoscriptsyntax as rs
import scriptcontext as sc
import Rhino, System

items=["A","B","C","D","None of the Above"]
ds=100/225  #display scaling factor
screen_point=System.Windows.Forms.Cursor.Position
screen_point.X*=ds
screen_point.Y*=ds
result=Rhino.UI.Dialogs.ShowContextMenu(items, screen_point, None)
print ("You chose {}".format(items[result]))

Running this on my laptop at 225% scaling, the menu then pops up pretty much where it’s supposed to, close to the location of the mouse cursor where one clicks, a little to the right and below.

Unscaled:

image
image1224Ă—672 32.7 KB

Scaled:

image
image518Ă—320 19.1 KB

Anyone know how to query the Windows display scaling factor on the local machine?

Hmm, looks like I’m answering my own questions today… found on StackOverflow:

import ctypes
ScaleFactor = ctypes.windll.shcore.GetScaleFactorForDevice(0)
print (ScaleFactor)

What was astonishing was that this also seems to work in IronPython 2.7 so I can be backwards compatible to V7. Probably doesn’t work on Mac though.

3

Hi @Helvetosaur,

This work here, even on monitors with dpi scaling enabled.

import rhinoscriptsyntax as rs

items = ["A","B","C","D","None"]
rc = rs.PopupMenu(items)

– Dale

4

@dale Well, I don’t know what to tell you - as the picture above attests to, PopupMenu() doesn’t work correctly here on either of my two computers/monitors with different dpi scaling. And this in Rhino 6, 7 and 8. Adding the correction (225 for my laptop and 150 for my desktop) via the script makes it position perfectly.

Are you testing with a 4K monitor?

1 Like
5

I’m having the same issue and still can’t figure out how to make it work.

Code is copied from sample code here

import rhinoscriptsyntax as rs

items = "Line", "", "Circle", "Arc"
modes = 2,0,0,0
result = rs.PopupMenu(items, modes)
if result>=0: 
    rs.MessageBox(items[result])

sys info:
Rhino 8 SR15 2025-1-19 (Rhino 8, 8.15.25019.13001, Git hash:master @ 74164bdf5469c2f269746857c54b8c44b74c7b24)
License type: Commercial, build 2025-01-19
License details: Cloud Zoo

Windows 11 (10.0.26100 SR0.0) or greater (Physical RAM: 32GB)
.NET 7.0.0

Computer platform: LAPTOP - Plugged in [100% battery remaining]

Non-hybrid graphics configuration.
Primary display and OpenGL: NVIDIA GeForce RTX 4060 Laptop GPU (NVidia) Memory: 8GB, Driver date: 11-6-2024 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 566.14
> Integrated accelerated graphics device with 4 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port
Primary OpenGL: NVIDIA GeForce RTX 4060 Laptop GPU (NVidia) Memory: 8GB, Driver date: 11-6-2024 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 566.14
> Integrated accelerated graphics device with 4 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port

OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
GPU Tessellation is: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)

Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High

Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 11-6-2024
Driver Version: 32.0.15.6614
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 8188 MB

6

Hi,

I get the exact same issue as you @Helvetosaur, and just as you mention this seems to be a problem for screens with higher resolutions. On a regular 1080p screen everything works, but on a 4k screen all forms pop up at a shifted location that corresponds to the scaling…

As an alternative solution to your question about querying the scaling locally, I’ve had some success using the “LogicalPixelSize” (see below) on the Rhino window. I then scale the form insertion point (that I base on the cursor position).

import Rhino as rc
scale_factor = rc.UI.RhinoEtoApp.MainWindow.LogicalPixelSize

A problem for me now is that I only have access to the insertion point for the “ShowContextMenu” from your example, not the other forms I need (like checkbox forms etc). One could do a fully manual eto form for this, but it’s nice to have the simple forms for less complicated things.

Bumping @dale in the hope this can be fixed since @Helvetosaur is not alone in getting this popup location bug for 4k screens.

7

Hi @flarback,

Just to clarify, something like this works?

#! python 3
import Rhino
import System

def MyPopupMenu(items, modes):
    size = Rhino.UI.RhinoEtoApp.MainWindow.LogicalPixelSize
    point = System.Windows.Forms.Cursor.Position
    point.X = point.X * size
    point.Y = point.Y * size
    return Rhino.UI.Dialogs.ShowContextMenu(items, point, modes);

def TestMyPopupMenu():
    items = "Line", "", "Circle", "Arc"
    modes = 2,0,0,0
    result = MyPopupMenu(items, modes)
    if result >= 0: 
        print(items[result])

if __name__ == "__main__":
    TestMyPopupMenu()

I don’t have a 4K monitor to test…

Thanks,

– Dale

8

This works for me.

import Rhino
import rhinoscriptsyntax as rs

items = ["Test", "One", "Two", "Three"]
modes = [1]

screen_point = rs.GetCursorPos()[1]
scale_factor = Rhino.UI.RhinoEtoApp.MainWindow.LogicalPixelSize
view_point = rs.XformScreenToWorld(screen_point/scale_factor, screen_coordinates=True)
result = rs.PopupMenu(items, modes, view_point)
9

Seems like we can do better. I’ve logged this.

https://mcneel.myjetbrains.com/youtrack/issue/RH-86577

– Dale

10

Hi!

Almost, divide by the size variable in your example rather than multiplying (like in the example @Measure gave).
Otherwise this is just what I have done to work around the bug for 4k screens.

Thanks for logging this!