Is there a way to find coercion dots?

[jz_007]

When you wire (for example) a double precision number to a VI that expects an unsigned integer, a little coercion dot appears on the vi.

Surprisingly, these do not appear on the warnings list, despite the enormous potential for cock-up (and I've had several, believe me).

Is there any other way of finding all occurences of these coercion dots, in a similar way to finding all breakpoints etc.

Or should I just change all numeric variables to doubles, just to be on the safe side? Wouldn't this use heaps of RAM, or doesn't it matter with modern computers?

Thanks in advance

Joolz

[VIGuy]

I don't know of any programmatic or LabVIEW ide way to find them all, but I know a way that will help you find them (assuming LV 6i or 6.1, might work on older versions).

- From a VIs menu bar: Tools -> Options -> Colors
- Uncheck "Use default colors"
- Change "Coersion Dots" to a bright red color (or whatever you like).
- Press "OK" and watch your diagram light up like a Christmas Tree!

Good luck.

[jz_007]

Good idea - thanks!

In case anyone from NI reads this, I'm going to have a bit of a rant:-
Why do we always have to find workarounds for this sort of thing? I didn't even realise you could make 1,000 + 1,000 = 255 when I started using Labview - other languages I've used won't let you do this at all - but you don't even get a warning here! Now, I find myself with three months' useless data, and no way to search for the cause of the problem.

Meantime, I've got a VI downloaded from the forum to help rename a collection of VIs, because there's no other way to save a snapshot of your work, or even make sure the VI you think is loaded is *actually* the one that is loaded.

Does no-one at NI listen, or am I the only one that finds certain aspects of LabView
immensely frustrating, spoiling what *should* be a moderately simple program for non-geeks. The more I use it, the more I feel that VB would actually be simpler.

BTW, the forum search is rubbish too - I only want hits from the Labview section - why would I be interested in hits about measurement studio etc? Take a look at http://www.utteraccess.com/forums/ubbthreads.php?Cat=
for a better way of doing it.

[Ben]

Options>>>Debugging

alows you to show warings in the error box.

Coercions are concidered Warnings.

Be prepared to do a lot of looking. Un-wired inputs to a VI are also listed as warnings.

Ben

[jz_007]

I've got the warnings option on as you suggest, but coercions do not appear in the warnings list, despite a rigorous trawl through all the unwired inputs!

Maybe coercions are warned in some versions of LV but not others - I'm using v6.1

Cheers

Joolz

[Spaz]

No coercion warnings here in 6.02 either. If anybody knows a way to add coercions to the listings warnings, via .ini switch, etc. I'd really like to know.

[Ben]

My MISTAKE!

Please forgive me. I am not sure where I got that misconception.

It was probably that same dream where I was able to right-click and do a "serach and Replace All".

I really need a vacation. But then again, I'd only end up using the time to work on the LV Challenge.

Once again, please forgive my error.

Ben

[Ben]

My MISTAKE!

Please forgive me. I am not sure where I got that misconception.

It was probably that same dream where I was able to right-click and do a "serach and Replace All".

I really need a vacation. But then again, I'd only end up using the time to work on the LV Challenge.

Once again, please forgive my error.

Ben