From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
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)
I consider this idea complete by the introduction of Environments in 2016:
https://zone.ni.com/reference/en-XX/help/370052W-01/tsfundamentals/infotopics/tsenv/