Right clicking displays the menu far away from the mouse (4k montior)

[collinpc]

---

@Lbee11 wrote:

I've also had this issue, I have a 4 screen setup and it causes a nightmare. I have found a work around. The issue goes away if I right click on the block diagram and pin the pallette, further right clicks and any menu interactions work as normal. As soon as I unpin the pallette, the issue returns!

I have no idea why this works.

---

Thanks for this. While not ideal this is a pretty easy fix

[wiebe@CARYA]

---

@collinpc wrote:

---

@Lbee11 wrote:

I've also had this issue, I have a 4 screen setup and it causes a nightmare. I have found a work around. The issue goes away if I right click on the block diagram and pin the pallette, further right clicks and any menu interactions work as normal. As soon as I unpin the pallette, the issue returns!

I have no idea why this works.

---

Thanks for this. While not ideal this is a pretty easy fix

---

Do get the same with the probe window?

Seems to me LV struggles with floating windows. So any floating window (palette, probe) disrupts proper handling of coordinates? I'm not at the system anymore so I can't try... I don't use pinned palettes a lot.

[RavensFan]

Update on this thread.

I was coming across this problem again, remembered the thread and searched for it.

My situation:

23" 16:10 monitor is display 2 sitting to the left 1680 x 1050 100% font  (monitor probably 12 years old)

15" 16:9 laptop screen is display 1 sitting to the right  1920 x 1080 125% font (displays are "extended" so I can see some stuff on one screen, other windows on the second)

Right click on a LabVIEW window on the left screen and the palette pops up down and to the left.  Or click on a menu such as File, it appears down and bit and to the left.  If the windows is to the left of that screen, then the file menu can't be seen because it's off the edge of the screen.

Now if I put a floating palette, pinned functions/controls, navigation, or probe window on that screen, then right clicking or using the menu bar puts the items right where they should be.

It seems that the problem happens when the font scaling for each display is different from each other,  When the same it doesn't seem to have menu/palette problems.

My old monitor recommends 1680 x 1050 and 100%.   I'm fine with that appearance.

The new monitor recommends 1920 x 1080 and 150%.  But 150% is too big for me, and 100% is too small.

So the best fix for me is keeping a window such as navigation on the display 2/old monitor.

[EZ-TechStop]

I have yet to find anyone who has successfully implemented a 4k multi-monitor scheme with LabVIEW 2017 SP1.  I am able to use my second monitor to run highlight execution on a block diagram and to probe wires, but cannot effectively code on a second screen.  This was obviously and oversight when the LabVIEW windows interface was developed.  Some of these issues become every more evident when you try to use the mouse position on a 4K monitor.  

Duplicating a laptop screen and an external monitor is one solution. (I'm not advocating developing block diagrams to fill a 4K screen either)

Running at 1080p on laptop and external screens duplicated is a solution.  

See this link for other fixes when running at 4k (such as misplaced menus): https://forums.ni.com/t5/LabVIEW/Minor-bug-odd-dropdown-menu-behavior-in-Windows-10/m-p/3575457/high...

Has anyone tried turning off their laptop screen and running dual 4k externals?  

[RavensFan]

---

@EZ-TechStop wrote:

  This was obviously and oversight when the LabVIEW windows interface was developed.   

---

How can it be an oversight when the LabVIEW windows interface was developed which was developed long before anyone invented 4K screens?

[Ola_A]

I just noticed this problem for the first time, running LV2015 on laptop (1920*1020/125%, two monitors at 1920*1200/100%). Maybe it is the first time I do some serious coding since upgrading to windows 10!

By accident I ran into a solution that might work for me and others, try undock/dock the laptop!

I started this morning with the problem, restarted laptop with same results. While reading this thread I had to run away with my laptop so I undocked it. Later I resumed and saw that the problem was gone, strange!

[magicbean]

LabVIEW is the only one of many development tools that I use where this doesn't work correctly; it's very disruptive to coding. Most of the other tool developers seem to have had less issues.

There are other problems with LabVIEW and high resolution monitors, not only context menus (e.g. the installers don't work very well at high resolutions).

Pinning the function / control menus only sort-of works although it seems to be true that clicking on a pinned menu on your working screen seems to always fix the problem temporarily. It doesn't take long for the context menus to start appearing in stupid places, though. I don't mean a bit to the right or left, I mean off-screen completely.

[Bill_in_Detroit]

I had this problem with a Dell laptop and a Dell USB C docking port with two external monitors.

The only thing that worked for me was to make sure all of the monitors were set to their maximum native resolution and scaling set to 100%.  Changing any of the monitors to 125% or higher brings the problem back.

Now, if only I could get the windows I have open to stay where they were when the screen saver comes on (or I lock the keyboard).

Bill

[az_ltr]

I am seeing the same thing on LV2019 SP1.   Does anyone know other than probe closure and pinning any fixes rather than workarounds?

[EZ-TechStop]

The best setup I have found when using a Windows 10 laptop:

Set my laptop's display to 1920x1080 pixels

Attach two 2K monitors using a dock 

Set one of the external 2K displays as the primary display (I use my laptop display as the 3rd and far-right display.  

This configuration seems to resolve all issues.  I have not tried to run this configuration with 4K external monitors but I believe it would work. 

Best,

Zach 

EZ-Techstop.com