LV2017 bug using Plot.LineStyle ?

[Blokk]

Hello,

See the snippet below. I just discovered it today. I can manually set the plot style to value "1" (long dashed lines). But if I programmatically either set its value to "1", or even just read it using property nodes, the real style switches to value "2"!

LV 2017 32 bit.

Edit: very strange. Try it, set the style of the Graph to the second option (value 1, long dashed lines). After this if I call the Lava Code Capture tool from the Tools menu, it will show the Graph FP with plot in style value "2"!!!

EDit: just to show the FP before I run the VI:

[Blokk]

Actually you do not need any property node to produce the bug: just place an XY Graph on the FP which has a curve displayed. Set the line style to the second option (value/index 1). Just run the VI. The line style will change to value 2 (third option). Any other style from the 5 options are not showing this behaviour.

[Blokk]

I confirm the bug also for LabVIEW 2016 and 2015 SP1 (32 bits). This is a big issue, this line style cannot be used, it requires manual reset always...

[dan_u]

I can reproduce this in LV2015 SP1 (32bits), but it only happens once the VI stops, which is not a big issue for me. As long as the VI is running, the line style remains at 1 when I set it to this style.

But when the VI is running I see another related issue: changing the line style from 1 to 2 doesn't work.

[Blokk]

---

@dan_u wrote:

I can reproduce this in LV2015 SP1 (32bits), but it only happens once the VI stops, which is not a big issue for me. As long as the VI is running, the line style remains at 1 when I set it to this style.

But when the VI is running I see another related issue: changing the line style from 1 to 2 doesn't work.

---

No, the issue is more serious. I build an executable from of my project, and this behavior does not let the user use the long dashed line during runtime! In my application the user can save and load "graph style" configuration files. When a saved config is loaded, the plots with "line style 1" appear OK. HOWEVER, doing any operation programmatically on the actual plot will switch the linestyle to value "2"! Such programmatic feature in my application when the user selects a sensor, and I highlight the corresponding curve for easier observation (I increase the plot width to max and back to original stepwise in ~200 msec).

This bug renders this feature useless!

Edit: the snippet shows one of my problems. But I see already several other ones in my feature list... So I have to tell the end user: just use all the line styles, but expect the second one has a bug 🙂

[dan_u]

Ah true, any operation will change the line style to 2. Yes, that makes line style 1 pretty useless.

[Blokk]

Could someone from NI state whether is this a bug, and assign a CAR if so?

Thanks! 🙂