LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
0 Kudos
blackburnite

Global LV setting to ignore separate compiled setting of projects, classes, etc.

Status: Declined

It's better software engineering practice to modify your source with your desired settings rather than having environment settings override things.

A new setting in Tools > Options > Environment to go along with "Separate compiled code from new files" which tells LV to honor that global setting instead of the one applied to projects, classes, etc.

 

When you pull in legacy projects or other tree-type files which have the "separate compiled" option unchecked, anything new you make in them also has it unchecked even if your global setting is to separate.



I saw my father do some work on a car once as a kid and I asked him "How did you know how to do that?" He responded "I didn't, I had to figure it out."
3 Comments
Christina_R
Active Participant
Status changed to: New

We generally don't want global options to override project, library, and class settings. Can you please tell me why you can't modify these files when you pull them in?


Christina Rogers
Principal Product Owner, LabVIEW R&D
joerg.hampel
Active Participant

I agree with Christina. I would not want the global setting to actively change existing code, especially as there are many ways to update it manually (see https://hampel-soft.com/blog/separate-compiled-code-from-source/).




DSH Pragmatic Software Development Workshops (Fab, Steve, Brian and me)
Release Automation Tools for LabVIEW (CI/CD integration with LabVIEW)
HSE Discord Server (Discuss our free and commercial tools and services)
DQMH® (Developer Experience that makes you smile )


Christina_R
Active Participant
Status changed to: Declined

It's better software engineering practice to modify your source with your desired settings rather than having environment settings override things.


Christina Rogers
Principal Product Owner, LabVIEW R&D