Extremely small cursors on both the front panel and the block diagram

[zoom_007]

High compatibility with DPI has only become a problem for Win10 since Image 1703.
Unfortunately, Win10 Image 1709 did not fix the problem with LabVIEW.

[kaneem]

Hi zoom_007, since I see the "small cursor" issue in some of Microsoft own products (MS Word for example) I am wondering if there is a particular graphic hardware/driver issue (related to Windows update or otherwise) that is causing this. I am certain Microsoft would have fixed this issue as it occurs with their own Office Suite (at least that is what I see here). So, in an effort to identify any similarities with others having this issue, this is what I am running:

• Processor Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz, 3601 Mhz, 4 Core(s), 8 Logical Processor(s)
• Resolution 3840 x 2160 x 60Hz
• Intel(R) HD Graphics 630 (Motherboard graphics - not used)
  • c:\windows\system32\driverstore\filerepository\igdlh64.inf_amd64_0745f11ce6fc197c\igdkmd64.sys
  • (21.20.16.4534, 10.52 MB (11,033,056 bytes), 2/11/2016 12:05 AM)
  • Driver Version 21.20.16.4534
• NVIDIA GeForce GTX 1070 (Active display adapter)
  • c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_ce1961376673184c\nvlddmkm.sys
  • (22.21.13.8541, 14.88 MB (15,600,248 bytes), 29/08/2017 9:25 PM)
  • Driver Version 22.21.13.8541

[zoom_007]

Hi, kaneem,
You have not specified which Windows Image you now have. I guess, according to your description, you now have Image-1703 (spring 2017).

If you are upgrading Windows to Image-1709 (November 2017). Then the problem of MS-Word, MS-Paint etc. disappears. But with LabVIEW, the problem remains.

I've discussed this before.

This is not a theoretical assumption, but a practical experiment on two different laptops (HP and DELL). Both of them have processor i7 and resolution 3840 x 2160. all three Windows Image (1607;1703 and 1709), have current graphic card drivers (October 2017) for Windows 10-64bit.

You already know the results of the experiment.

[kaneem]

Hi zoom_007,

I am currently using 1703. I do not recall you mentioning that MS applications work correctly under 1709, only that 1709 did not fix the LabVIEW problem, but regardless that is interesting.

It is peculiar that the cursor API that got fixed in 1709 worked for some applications and not others (assuming a common API), or did 1709 also include application patches for it's MS suite?

For us, falling back to 1607 only helps us in a small way. We deliver applications to built in LabVIEW to customers, and as you would expect, not all customers will like being told to downgrade their OS just for our software.

In summary zoom_007, I do agree with you that this is a critical issue. But for us, as we use LV7.1.1, and are well out of the support cycle, I doubt we will see a fix if it is required by NI to do so. For us the ideal outcome would be for Microsoft to "unbreak" the API!

[zoom_007]

Hi kaneem,
- With the Image-1703, Mircosoft wanted to completely remove old MS-Paint. Should only exist MS-Paint-3D. Before publishing Image-1703, MS decided to use both MS-Paints (that is a fact).
- Since Windows Image-1703, LabVIEW and e. g. the old MS-Paint have a small cursor (that is a fact).  Paint-3D had no problem with a small cursor (if I remember correctly).

Here's my guess.
I don't know where exactly Mircosoft made a mistake, but apparently Mircosoft only optimizes the new interface (3D) or corrects the reference to the new interface (Windows Image-1709). LabVIEW is probably still using the old interface/reference.

If my guess is correct. Technically, the bugfix shouldn't be difficult.
But you need to know what Windows has actually changed at this level. And that won't be easy.

[DuncG]

I had this same problem and solved the issue by going through the Intel graphics control panel.(right click on desktop Graphic Properties). The default scaling setting is Maintain Display Scaling. (this is what is generating the problem) Changing it to Maintain Aspect Ratio solved the problem. On LabView and other programs.

Hope this helps.

[zoom_007]

It's interesting. Has anyone else tested the suggestion? 

[JORY]

I am working with LabVIEW 2016 on a Microsoft Surface Book and it happend about three month ago: The cursor became almost invisible. I bought some glasses.

Also, the MAX switched to some tiny fonts (at a different time, independently).

This is a bug! NI, please correct it.   

[RavensFan]

How do you expect NI to fix what seems to be a Windows problem?

[diarmaede]

"How do you expect NI to fix what seems to be a Windows problem?"

I use many, many Windows programs.  I have only seen the problem in LabVIEW.  Bottom line is that the problem makes LabVIEW almost unusable, and I will be highly annoyed until NI and/or Microsoft fix it.