Missing help information?

Question

I find that some labview objects do not link to any description or help information. For instance, when I drop a control, say the "file path control" from the "string & path" palette onto the front panel of a vi, there is "no description" available in the context help panel, there is no "help" option on the associated drop down menu, and there appears to be no corresponding entry in the labview help documentation when searching for "file path control". This seems to be true for most, but not all of the front panel controls. It is also fairly common to have difficulty finding results on search terms entered into the "search the labview help" dialogue. Very often I find quoted help entries on the labview web site that I can't locate on my machine. For instance, I spent a very long time searching the installed help documentation trying to figure out how to convert between the numeric value returned by a color box constant and the actual color contained within. A quick google search returned a Knowledge Base entry on your website titled "How Does a LabVIEW Color Box Interpret a Numeric Value for Color?" This entry quotes help documentation from a Labview product manual that explains how the color box constant is encoded. I realize that the entry on my machine may not be exactly the same as the entry quoted from your published manual, but darned if I can find anything that gives the slightest hint in my installed help documents. Is there something wrong with my labview installation?
global variables make robots angry

Answer 1

Sorry, I wasn't very clear in my first post. When I place a pre-written function on the block diagram, a handy description pops up in the help panel,  a detailed description is available in the labview help documentation and it has a nice help option on its drop down menu that I can click on for info. The controls that I select for the front panel are, of course, pre-written functions as well. That is to say; they were created by someone other than me and they do things in a specific fashion that might not be totally apparent (to a dummy like me). Because the drag and drop interface for building the block diagram is similar to the drag and drop interface for building the front panel, it instinctively feels like there should be some sort of description there of the control functions that come with labview, just like the descriptions of the block diagram functions that come with labview. I think what I was looking for might be the help button that I've managed to find by right clicking on the control object, then selecting properties from the drop down, then looking in the lower right hand corner of the properties section. Funny thing is, I read the path properties entry from the file path control that I dropped on the front panel, and I still can't figure out how the control selects the default search folder if it isn't specified, and I'm still not sure whether I can somehow programmatically set the default folder for all "file path controls" on the front panel at once. I'm still searching for that answer in the installed documentation because I feel like I should avoid posting lots of questions to the forum unless I'm sure that the answer isn't sitting right there in the documentation somewhere, which leads me to the second example, the color box constant conversion thing.
I read that same help description that you found which is why I was so confused to find that the number I was looking at was not a hexidecimal and had a different number of bytes than the help file specified. It turns out that if you create a color box constant on the block diagram and pick a color, any color, nothing up my sleeve- then create an indicator to output that color, you'll find that the color is not a hexidecimal alphanumeric with six values and three bytes, it is instead represented by a thirty two bit integer. that's one more byte than in the help description, and the integer didn't seem to have an obivious pattern in it that would give away how to turn a red green blue, three byte number into the 32-bit integer that the color box constant shoots out. So here's the official description from national instruments that tells me what the heck is going on with the color box color to integer conversion:
"A color is represented by a 32-bit integer, with the lower three bytes representing the red, green, and blue components of the color. For a range of blue colors, create an array of 32-bit integers where only the values of the low bytes change (the low byte contains the blue component). To create a range of gray colors, you need to create an array of 32-bit integers where the red, green, and blue values of each element are the same."
so you see there are four bytes with one byte empty that you have to assemble into an integer. or decode by doing the reverse.
and the quoted description is from the LabVIEW Picture Control Toolkit Reference Manual Version 1.0. But of, course, the description of how to convert from an integer into a color and vice versa must be in the regular documentation somewhere, because it's a fairly fundamental thing. So I looked in my installed help documentation again to see if I could construct a search phrase to find it, so I would be a little wiser about how to search for specific info in the help files, but I'm just not able to locate it. And, of course if I create a color box control and go into the properties and find the properties help button for the Framed Color Box Properties Dialog Box it doesn't actually say anything about what happens between you picking a color and it shooting a number over to the block diagram, which makes me think "Ok. there is a description of this pre-made control somewhere else, and I'm just not looking in the right spot to find it, because who would give you a big ol' palette of these pre-made controls to use, and leave you wondering what the heck some of the controls are doing when you use them?"
So I was thinking that I'm not looking in the right spot for documentation, or I'm not searching in the best way, or that maybe I'm missing part of the help documentation or something.
global variables make robots angry