error 1000 occurs when changing unit

[Jean-Louis]

It seems to be a LabVIEW 7.1.1 bug :

> When changing interactively the unit of a command or indicator, accessing attributes nodes of other front panel objects returns an error 1000.

Any workaround will be very appreciated.

VI attached is an illustration of this problem :

> run the VI

> change Length 1 unit (by exemple m --> mm ou in)

> error 1000 occurs and read value is incorrect.

[daviddelebecque]

Hi,

This is not a bug. We cannot change name labels at run-time. Changing control names requires recompile of the VI, and when a VI is reserved, we do not allow any operation that would cause the VI to be recompiled. The property node in this case returns error 1000, which indicates that the VI is not in the valid state for this operation.

http://digital.ni.com/public.nsf/websearch/FD0257A4429A26E886256992006ACC0F?OpenDocument

BUT, LabVIEW 8.0 seems to allow that change dynamically....

Regards,

David D.

Application Engineer - NI France

[Jean-Louis]

Hi David,

I am not sure this is not a bug since this VI works fine in LabVIEW 7.0 !

For your information, using unit allows changes interactively or programmatically at run-time within the same unit class (per example mm --> cm or in).

In the attached VI, if you don't retrieve property node, error 1000 doesn't appear.

Jean-Louis Schricke
MESULOG

[GerdW]

Hello David,

I also tested the example of Jean-Louis and I got the same error message (in LabView7.1).
BUT: we are not talking of labels we are talking of units! LabView normally takes care of units and their conversion. It's no problem to change the unit (to a compatible one) and LabView automatically changes the value of that control (e.g. 25.4 mm to 1 in).

So: Why does LabView generates an error when I change the unit of a second control when accessing the first control via property node?

Message Edited by GerdW on 11-07-2005 09:43 AM

[daviddelebecque]

Hi,

I understand the problem and the error is coming from a a property node reading the value of a boolean control. The problem appears with LV 7.1. We can say it is a bug and it is corrected in the version 8.0 of Labview.

Regards

David D.