[EMAIL PROTECTED] wrote: > Instances of a typedef do not change their value when the default > value of the typedef changes. Nor would you want them to 9 times out > of 10. Stick with the VI returning a constant.
That's a pity- I've used them for enumerations in the past and this thread had made me decide to try using them as constants at some point. Though I see how much of a cockup it could be. There's no difference though between dragging a subVI and dragging a typedef, so I'll probably still give the subVI approach a try. I've been storing constants in globals before now, but it's always bothered me that I can't write protect them. > Is it easier to drop one constant [from the palette or file system] > and then select which subpiece to use than it is to just select which > constant you want [from the palette or file system] in the first > place? I'm not opposing your general comments that a simpler way to Editing would be nicer. But I'd spend more time using them than editing them so single VIs would work better. A VI could be written to simplify the editing- let you create and edit variable files from existing templates, and then give you a VI in a "constants" subdirectory that can be dragged to the diagram. Keeping all the VI constants in one directory under each app with one item in each VI should make it easy to iterate through them all to build an editing screen. Not that I'm offering- I don't think I'd use enough constants for it to be worthwhile. -- Dr. Craig Graham, Software Engineer Advanced Analysis and Integration Limited, UK. http://www.aail.co.uk/
