LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

The same type and red coercion dot

Hi!

 

A small project is attached to show how red coercion dot appears if you remove"lib type definition.ctl" from library to a virtual folder. It is interesting that this affects only class property nodes. It does not affect class accessors ("setters") and indicators. The same happens if you move "type definition.ctl" from virtual folder to the library.

 

Picture shows changes in "vi in library.vi" block diagram.

 

red dot.jpg

 

The application works but a peaceful bad feeling remains ...

 

There are discussions on this NI forum about typdef controls. It seems that using type definitions can cause serious problems if used together with property nodes. What would be suggested in these cases?

 

Regards,

 

Ljubo.

 

 

0 Kudos
Message 1 of 3
(2,806 Views)

I can't unfortunately look at your code right now, but there are a couple points to be made:

 

  1. I'm not sure the problem you show is a bug. Moving the control file out of the library and into a virtual folder in the project changes the type definition because it has a different name.
  2. LV does at times show spurious coersion dots, but I have never seen it cause a functional problem - let alone a serious one.

Mike...


Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 2 of 3
(2,756 Views)

Just right click on lib type def and create constant. I dont thinks that will appear...Try and let me know

 

Thanks

--------------------------------------------------------------------------------------------------------
Kudos are always welcome if you got solution to some extent.

I need my difficulties because they are necessary to enjoy my success.
--Ranjeet
0 Kudos
Message 3 of 3
(2,749 Views)