Odd view of Array Probe

[RavensFan]

I just finished installing LV 2015 and started looking at the new features.

One I know I'll like is the improved appearance for view arrays with a probe.  I tried it out and saw an odd appearance to it.

Why is the array shift slightly to the left.  The left part of the index is off the left side of the probe.  There is plenty of extra space on the right.  Adjusting the bottom scrollbar will clean it up, but that shouldn't be necessary.

As anyone else seen this?

One other feature I thought might have been added to this, but I guess wasn't, would be a way of showing the size of the array in each of  its dimensions.

[RavensFan]

Interestingly, converting the array to 2-D or 3-D and creating the probes for those, it looked okay.

Going back to making them 1-D arrays, it went back to being shifted off to the left.

[kkleine]

Hey RavensFan!

We greatly appreciate all your contributions to the forum!

I could not reproduce this issue on my machine. The array probe has very similar behavior regardless of how many dimensions the array is that I am probing. When I probe a 1D it does not have a horizontal scroll bar:

Have you created a custom probe? I believe Right-Click » Probe defaults to opening the last type of probe selected. You can explicitly open the generic probe using Right-Click » Custom Probe » Generic Probe.

Does this issue occur in all VI's you test?

Regards, 

Kevin

Applications Engineer 

National Instruments 

http://www.ni.com/support

[RavensFan]

I have not tried it with any other VI's up until now.  It was strictly a simple brand new vi, array constant to array indicator to just play with it.  So I opened up a project I've been working on (which I'll be keeping in LV14 for the time being.)  In experimenting, I learned the common factor here.

When I posted the picture in the original message, I was working on my laptop from home.  I was using just the laptop screen which has a lower resolution of ( )

When I tried to replicate that here at work, my laptop is docked and I'm looking at twin 24" monitors with a resolution of 1920x1080.  I could not replicate it.  The window looked fine, pretty much like yours.

So I undocked and repeated, and I had it behave just like it did originally with 1-D arrays shifted over and off the left side of that panel with scroll bars present.

I redocked, kept that probe open, it did not fix itself, but when I created another new probe, it behaved fine.

So I think the problem is that whatever code is responsible for displaying that array (and why only 1-D and not other N-D arrays) miscalculates whenever the window resolution is smaller than some value.

So if I can recommend you trying again, but using a laptop with a lower resolution, that might be able to confirm my theory.

[RavensFan]

I did some experimenting by changing the screen resolution while docked.  I think the problem occurs whenever the vertical resolution is somewhere less than 1024.

I changed the resolution on my main 24" screen, had the block diagram on that screen, and the probe display on that screen when I created a new probe.  I did this for each of the resolution settings my driver had.  (Some of these I would never use intentionally because of distorion with respect to my monitor's aspect ratio.)

  The results:

1920 x 1080 (my defaults for docked laptop)  GOOD

1680 x 1050  GOOD

1600 x 1200  GOOD

1440 x 900  BAD  (Both scrollbars and offset)

1368 x 768  (the default resolution for undocked laptop using built-in screen) BAD

1280 x 1024  GOOD

1280 x 960 BAD

1280 x 720 BAD

1152 x 864 BAD

1024 x 768  BAD

800 x 600 BAD

One other thing I tried.  I changed my #2 monitor to be 1920 x 1080.  Set my #1 monitor to be one that was bad.  Moved my block diagram to the #2 monitor, but left the probe window on the #1 monitor.  Here I got mixed results where the array display was not offset to the left, but the scrollbars still showed up.

Hopefully this gives some clues.

[kkleine · Accepted solution]

Hey RavensFan,

I tested similar resolutions on my machine and am seeing the same behavior on the probe display. I will escalate this accordingly and be sure that our R&D department is aware of the issue. Thanks for pointing this out!

Regards, 

Kevin

Applications Engineer 

National Instruments 

http://www.ni.com/support

[RavensFan]

Good.  I'm glad you could replicate it.

Not a huge problem, just a nuisance.

If you get a CAR number assigned to it, please post it here so we can track it in the future.

Thanks.

[Jacobson-ni]

CAR #544435 for future reference

[ChrisStrykesAgain · Accepted solution]

CAR 544435 has been fixed in LabVIEW 2016. Please see the LabVIEW 2016 Bug Fix List for more information.