Right, me too. But yesterday I was inside a VI that didn't have any error terminals (just array functions), so to get an error constant, I had to place a VI of some type and create a constant from it then delete the VI. Seems intuitive to me to put the constant on this palette.
Same here. I always have to place an error terminal on the front panel just to be able to right-click and create a constant. I think most users out there probably do this same thing and this constant could save unecessary steps. You have my vote!
I guess this is one of those "Well, I can do this with a merge VI, so why does NI have to spend the time to add this to the palette?" But then the error cluster is so ubiquitous that it could almost be considered its own "special" datatype, like a DBL, or a string, and we have constants for those. I'll vote for this idea, but won't cry if it doesn't appear.
> How many mouse clicks do you think it would take to find an error constant in the palettes and drop it on the BD?
Good question.
3 clicks to get to the constant, (no tabbing, if you tab).
6 clicks to get to a function of some type, create a constant off of it, and delete the host function (plus a few tabs --> I'm still a tabber, but I'm not going to hold that against me).
I also like the idea that a "no error" constant would have a distinctive icon, rather than looking like every other cluster-constant-viewed-as-an-icon on the BD.
