Wings 3D Development Forum

Full Version: Context menu on the wrong screen
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I have 2 screens and sometimes I like to record tutorials.
So I moved my Windows main screen to screen 2 to get my Start bar out of my videos.
Loaded up Wings, right-clicked to create a cube, and the context menu comes up on the main screen, not in the middle of the Wings window like it has for 500,000 years.

I need to have this behaviour changed.
Hi some_yahoo

That's a bug already reported in the Bug sessio.
Despite the title, follow this link
Fixed] Wings Crashes on HDMI Monitor in 3 Monitor Setup and download the patch.
I recommend you to apply all of them available for v2.2.9 - I'm assuming that is the version you are using.
Applied all 4 patches, now the first menu comes up on screen 2 as desired, but subsequent menus come up on screen 1 and I can't click it.

...so I can click Extrude , but the X/Y/Z/Normal menu comes up on screen 1 and no amount of clicking selects anything.
some_yahoo , sorry about that. Very annoying indeed.
I'm going to take a look on it this night.
Hi some_yahoo
I took a look on the problem and I found I didn't updated the wings_menu.beam file with the latest fix I had applied last month. Blush

Please, just download and apply the wings_menu.beam path again. (Wings3D needs to be restarted after that)
It still acts the same, and it gives me this:

Dump written 2023-5-7_13-39
Version: 2.2.9
Window: dialog_blanket
Reason: badarg

Short stack trace:
[{erlang,send,2,[{error_info,#{module => erl_erts_errors}}]},
{wings_menu,popup_event_handler,3,[{file,"wings_menu.erl"},{line,484}]},
{wings_wm,handle_event,3,[{file,"wings_wm.erl"},{line,1039}]},
{wings_wm,send_event,2,[{file,"wings_wm.erl"},{line,1015}]},
{wings_wm,do_dispatch,2,[{file,"wings_wm.erl"},{line,898}]},
{wings_wm,get_and_dispatch,0,[{file,"wings_wm.erl"},{line,693}]},
{wings,init_part2,3,[{file,"wings.erl"},{line,108}]},
{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,226}]}]

Long stack trace:
[{erlang,send,
[wings_menu_process,cancel],
[{error_info,#{module => erl_erts_errors}}]},
{wings_menu,popup_event_handler,3,[{file,"wings_menu.erl"},{line,484}]},
{wings_wm,handle_event,3,[{file,"wings_wm.erl"},{line,1039}]},
{wings_wm,send_event,2,[{file,"wings_wm.erl"},{line,1015}]},
{wings_wm,do_dispatch,2,[{file,"wings_wm.erl"},{line,898}]},
{wings_wm,get_and_dispatch,0,[{file,"wings_wm.erl"},{line,693}]},
{wings,init_part2,3,[{file,"wings.erl"},{line,108}]},
{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,226}]}]

OS: Windows 10 (build 22621), 64-bit edition
GPU: NVIDIA Corporation | NVIDIA GeForce RTX 3080/PCIe/SSE2

Also, I am on Win 11 if that matters.
Oh boy! Sad

some_yahoo, sorry again. I didn't pay attention what I was doing. Undecided
This time I forgot to upload a second file I have changed and also I used the newest version or Erlang to build them.

So, I recompiled them using the version used to build the v2.2.9 and it should be OK now - at least it worked for me (using the installed version).
Download the wings_menu.beam and wings_io_wx.beam from pathes repository.