From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Another strange "feature" of BD constants in debug mode

Related to but different from this question, here is another one.

When debugging a running VI, you can right-click on a BD constant (or in the case of an array or a cluster constant, an array/cluster element) and choose "Copy Data".

However, you cannot click, select and copy said element or constant. You can do that on the FP with an indicator, so it is not like a selection tool preventing any editing is a big no-no in terms of UI.

The odd thing is that you can select and copy the LABELS of objects on the BD (in debug/run mode)! Go figure...

It seems to me that NI arbitrarily decided: we won't bother letting people select constants on the BD (during debugging of a running VI). A contextual menu will be enough.

Am I missing something?

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

@X. wrote:

Related to but different from this question, here is another one.

When debugging a running VI, you can right-click on a BD constant (or in the case of an array or a cluster constant, an array/cluster element) and choose "Copy Data".


OK. With you so far.

 


However, you cannot click, select and copy said element or constant. You can do that on the FP with an indicator, so it is not like a selection tool preventing any editing is a big no-no in terms of UI.

Well, this actually makes sense. If you were allowed to select, you could change, and you cannot change running code. With front panel indicators, it's irrelevant, since the indicator would get refreshed when it's written to. Perhaps it wasn't worth the programming effort to allow selection and limit it to just allowing copy.

 


The odd thing is that you can select and copy the LABELS of objects on the BD (in debug/run mode)! Go figure...

I can't reproduce this. Can you provide details on how you are able to do this?

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

- I don't see how it makes sense: it suffice to disable editing (as in an indicator on the FP).

 

- Here is a picture of what I am talking about.

 

Here I am selecting the label of a control terminal:

 

ScreenHunter_002.jpg 

 

and here the label of an element of a constant cluster:

 

ScreenHunter_003.jpg

 

In other words, I am debugging and I can select (and copy) ANY label.

However, I cannot select ANY constant.

Doesn't make any sense to me.

0 Kudos
Message 3 of 6
(2,295 Views)

Ah, you've turned off the autotool and are explicitly selecting the labeling tool. Not really sure why the limitation exists. Perhaps it was an oversight, or perhaps it was seen as not worth the trouble, or perhaps it's a consequence of the constant folding of LabVIEW's compiler.

Message 4 of 6
(2,291 Views)

Ah, you haven't turned off the autotool..:-)

BTW, I meant to say, about FP indicators, that I don't understand your "refresh when it's written to". I, for a fact, CAN'T type anything into a FP indicator in run mode. But again, I have turned off the autotool...

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

Sorry - wasn't totally clear in my statement. I was following along with not being able to change the value of a control because you can't change the code at runtime, and saying that if you could change the value of the indicator after selection, it wouldn't matter since the value would get updated once you write to it.

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