Why does distribution kit editor require separate designation of "active project" from CVI?

[menchar]

When I go to edit a distribution, the nominal distribution is whatever distribution was last designated "active project" by the distribution editor, not CVI itself.  Is there some reason for this?  I'd think that if I had designated a particular project as the active project within a workspace, the distribution editor would also use that same designation for the active distribution.  But it doesn't.   This strikes me as a bt odd but maybe there's  good reason.

Mencchar

[Mert_A.]

The reason is that distributions are not strictly associated with a specific project. When you create a new distribution, it does pre-populate files, title, etc. from the active project, because that's the typical use case. However, there's no explicit association. The distributions are workspace associated, the idea being that it's reasonable that in a multi-project workspace, a distribution might include files from multiple projects.

I'll create an internal suggestion to consider adding a "primary project" to a distribution.

Mert A.

National Instruments