LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

again mixed signal graph and Labview 2012

I have just experienced a weird change in labview 2012 on the mixed signal graphs. In a preliminary analysis, it seems that the most critical behavior is related to the silver mixed signal graph, although i didn't have the time to test the standard one.

 

Straight to the point... the property "plot area size" not only resizes the plot area, but also the graph; this is in contrast with what happened previously in LV2011. If the graph belongs to a subpane and if the property "fit control to pane" is enabled, the area resize prevents the graph from correctly fitting the pane. 

Any suggestion?

cheers

m.

 

0 Kudos
Message 1 of 6
(2,953 Views)

This issue has been discussed via private support.

It is a bug ,a nd CAR #371045 has been filed

Vix
-------------------------------------------
In claris non fit interpretatio

-------------------------------------------
Using LV from 7
Using LW/CVI from 6.0
0 Kudos
Message 2 of 6
(2,886 Views)

I think that since this behavior is a regression (working properly until LabVIEW 2011 SP1) this should be fixed as soon as possible through a specific fix, without waiting for the next Service Pack.

This regression has been blocking the development of our application.

 

Could someone from the NI support give an answer, please?

Vix
-------------------------------------------
In claris non fit interpretatio

-------------------------------------------
Using LV from 7
Using LW/CVI from 6.0
0 Kudos
Message 3 of 6
(2,846 Views)

I also add that the bug affects both the 32 and the 64 bits of 2012 version

0 Kudos
Message 4 of 6
(2,841 Views)

I needed to rearrange my application in LV2012 and i had problems with mixed signal graph behavior.

Now i got LV 2013 and i still have the same problem.

So is this problem solved in some way that i don't know or it's best to just use LV2011?

0 Kudos
Message 5 of 6
(2,748 Views)

Schime, you are right. Unfortunately the problem still exist, although the support ensured that the problem would have been solved in LV 2013. We will try to contact the support again and see what happens.

0 Kudos
Message 6 of 6
(2,701 Views)