|
|||||||||||||
Why restrict to load the type pallets always from <user or NI>…Components\TypePalettes folder?
It will be very helpful I can configure my path to the load my custom type pallets, this will resolve the issue handling different type Palettes for different customers / projects / sequences.
Or even better, if given the option to associate the type pallet to sequence files / sequence model. Just like Edit -> Sequence File Properties -> Model Option -> Require specific model.
It would be nice to be able to associate type files with a project, (at least to the level that associating the type file with the project made it so that types file loaded into the types palette when that project was open, and double-clicking on the types file opened it in the types editor instead of notepad).
I think that requiring specific types files to be loaded in memory to **EDIT** a sequence file could be beneficial towards preventing type viruses, but I do NOT think it is good to require them to be loaded to execute a file. (associating types files to a sequence file could definitely help with this)
You must be a registered user to add a comment here. If you've already registered, please log in. If you haven't registered yet, please register and log in.
Post New Idea to submit a product idea. Be sure to submit a separate post for each idea. Note: the TestStand Idea Exchange is not the appropriate forum to submit technical support questions.The TestStand R&D team is committed to reviewing every idea submitted via the TestStand Idea Exchange. However, we cannot guarantee the implementation of any TestStand Idea Exchange submission until further documented.
My Profile | Privacy |
Legal |
Contact NI
© 2011 National Instruments Corporation. All rights reserved. | E-Mail this Page
|
||

E-Mail this Page