LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Labview returns an error and exits when "Yscale visible property" is set to False

Does or anyone know why or have experienced LaBVIEW popping up an error and exiting forcefully when Yscale visible? Property is set to false?

[BADGE NAME]

0 Kudos
Message 1 of 11
(4,947 Views)

BlessedK,

 

     How many times do we need to ask you to attach your VI that is giving you trouble?  You are probably "doing something wrong", but without seeing what you are doing, that's about all we can say.  It is possible that you've discovered a bug in LabVIEW, but it is more probable that something is missing in your code, or in your understanding of how a particular function works.

 

     We can certainly help, but we need to "understand the question", which can best be done (and sometimes can only be done) if you attach your VI.  Please try to make that a habit in future posts, as well (I'm beginning to sound like a broken record, attach your Vi, attach your VI,  attach your VI, ...).

 

Bob Schor

 

P.S. -- you remember, don't you, that I don't want you to attach a picture of your VI, but the VI, itself ...

0 Kudos
Message 2 of 11
(4,911 Views)
OK Bob, I am out of my desk at the moment but will post a vi once back 🙂 I have a feeling that I may have found a bug, but until I send the vi let me keep that open. I have another post about setting dedicated precision digits for Yscale and cursor positions, and a vi has been attached to I explain the problem. Still looking forward to a solution to that too.

[BADGE NAME]

0 Kudos
Message 3 of 11
(4,908 Views)
Hi Bob, I have just confirmed that this is another 2015 64-bit bug! Works fine on 32-bit. So I did absolutely nothing wrong I just hope an application engineer is reading these and planning to act swiftly on it?

[BADGE NAME]

0 Kudos
Message 4 of 11
(4,876 Views)
Seemingly Little but very annoying things 🙂

[BADGE NAME]

0 Kudos
Message 5 of 11
(4,875 Views)

Hi blessedk,

 

Please attach your VI as Bob mentioned earlier. I've installed LabVIEW 2015 64-bit on a test computer, but I was unable to replicate the issue with Modern Waveform Graphs, Charts, or XY Graphs. 

0 Kudos
Message 6 of 11
(4,823 Views)
Can you Send me the vi you tested? Thanks

[BADGE NAME]

0 Kudos
Message 7 of 11
(4,819 Views)

I'm not sure what Yiran's code was exactly, but I've attached my own recreation to try and test this out. I have not seen any errors. Can you please attach your code to your next post so that someone can really see the error you are? Is there any error code or message you get when you run your code?

Mathew H.
Applications Engineer
National Instruments
0 Kudos
Message 8 of 11
(4,791 Views)

Mathew,

 

     For reasons I fail to understand, BlessedK almost never attaches any code, despite repeated pleas from us to do so.  Instead, as you can see from recent posts, we are asked to "develop solutions" to "problems" that we cannot see.  Are we being played for fools?  I'd like to think that the answer is "No", just a case of pathological shyness or an "unwillingness to share" ...

 

Bob Schor

0 Kudos
Message 9 of 11
(4,784 Views)
Apologies Bob and Matthew, I am out of my desk and can only send mobile messages.

Matthew try replacing that with a mixed signal graph with say two or three plot areas and run the property node inside a loop with a case structure such that the Yscales alternate from visible to invisible or vice versa. ( that is, plot area one has a visible Yscale but plot areas two does not etc). Let me know what' you find. Once I am back I will send a vi too.

[BADGE NAME]

0 Kudos
Message 10 of 11
(4,769 Views)