Coersion Dots

[JÞB]

For the most part coersions can be broken down into two classes: lossy (e.g. 64L to I8) and safe (e.g. U8 to U16). Why is there only one color option for coersion dots?  Could the vi analizer have seperate settings for max allowable safe and unsafe  coersions?

[JÞB]

Again, Arestos Queue adds to a good idea.  I do like the idea of a tip-strip with the coersion information.  Jack's idea of adding it to context help would be valuable if it pointed to detailed help explaining the coersion and giving examples at boundary conditions

[AristosQueue (NI)]

> How about Context Help?

I forgot about that other idea. I'll remove my kudos from this idea since I've already kudos'd the other one. You're right... it's better. 

[JÞB]

Seeing the context help link-  I would submit this idea for the trash-bin.  Laura F. - is there a trash-bin status that the thread could be assigned to?

The context help and tip-strip implemetation is far superior to color / vi analizer methods to solve the original proposed problem restated as"Coersion dots are not informative enough"

[JÞB]

Hence- my deleteion of tag Good_Idea.

[Laura F.]

I'll send this along to Todd S. who manages the LabVIEW Idea Exchange.

[JackDunaway]

Wait... please see my second comment on Add Idea status- Rejected or Trash-bin. Any Idea that sparks a discussion should not be deleted. If anything is to be done, just consider it a duplicate of Context help on coercion dots to see what is the expected type.

[Manzolli]

Either Tip Strips or Context Help, but the color must be only one. With different wires, and the ones created by the user, some colors may "camouflage" the coercion dot.

[AristosQueue (NI)]

> Either Tip Strips or Context Help, but the color must be only one. With different

> wires, and the ones created by the user, some colors may "camouflage" the coercion dot.

I think pretty much everyone has come to (reluctant) agreement on this point.