08-26-2010 03:19 PM - edited 08-26-2010 03:20 PM
No, that doesn't look like what I have in mind. I want to set the value of the control to value given only its name. Both name and value are strings. As in the first reply to the post only it doesn't matter if you use This VI or another VI reference.
08-27-2010 07:30 AM
@kc64 wrote:
No, that doesn't look like what I have in mind. I want to set the value of the control to value given only its name. Both name and value are strings. As in the first reply to the post only it doesn't matter if you use This VI or another VI reference.
That will only work if the target object is a string data type. For other data types there would be confusion for example your pass the string "101" to a numeric that is set to display as HEX do we interpret the string as "101" "5" "65", ...
Ben
08-27-2010 09:23 AM
Right. So without having some property for the control as to its type, it is impossible to cast it to the correct type from a string without providing this direction externally. I think the best option in my case will be to store everything as a string and cast it at usage time to the correct value. Now that I say that, I wonder if the value could be stored as a variant and recovered using the type descriptors. The only way I know how to do that is by using OpenG's LabVIEW Data Tools but I don't have a license to deliver that in a product. 😞
08-27-2010 09:30 AM
Here is a Nugget I wrote to help out in this area of thought.
I am not telling you to do it that way. Just "giving you enough rope to ..."
Ben
08-28-2010 01:49 PM
kc64,
you mentioned:
@kc64 wrote:
The only way I know how to do that is by using OpenG's LabVIEW Data Tools but I don't have a license to deliver that in a product. 😞
What is the limitation you have not to use the OpenG toolkit inside a product?
The OpenG toolkit is licensed under the BSD license and that should put no limitations on redistributing besides an acknowledged notion in the about/readme/release notes.
You don't have to purchase a license to use and redistribute the toolkit.
Ton
08-31-2010 09:57 AM
@Ton--
Well, that's a good question. I had some idea that there was a more restrictive license that allowed for personal use (not for profit) but I suppose that I confused this with something else. I tried to find the license that I recalled but could not.
Thanks.