Change "Recent Files" to only display files within project

[PTortora]

In the Project Explorer, File >> Recent Files currently displays the most recent files opened in any project.  It would be useful if instead, it would display only files from the project associated with the Project Explorer window that Recent Files is selected from.

[AristosQueue (NI)]

zou -- your plan also doesn't work because *by design* every item in the project is listed exactly once somewhere. We at one point tested having VIs show up in multiple places (such as both within a library and within an autopopulating folder) and it just lead to lots of confusion.

[zou]

> *by design* every item in the project is listed exactly once somewhere.

My plan does NOT violate this rule.

How many times I have to tell you I'm adding a shortcut !  Not the VI itself !

For those VIs have no subVI.  My plan works just fine.

[AristosQueue (NI)]

A shortcut is the same as adding the VI. ALL entries in the project tree are shortcuts since it doesn't reflect disk except in the case of autopopulating folders. Multiple shortcuts to the same thing were the problem.

[zou]

My  shortcut is a Windows shortcut.  A .lnk file.

It shows up in the project as *.lnk.

I guess in your terms, it's a LabVIEW shortcut to a Windows shortcut file.

[AristosQueue (NI)]

Zou: Doesn't matter. It is still two items in the project tree representing the same actual VI.

[zou]

LabVIEW shortcut to a VI and its Windows shortcut are same ?!

It sounds like a LabVIEW BUG to me.

[zou]

I don't know how much LabVIEW insight you know.

I think you interpret the problem incorrect.

As I see it, LabVIEW handles Windows shortcut properly in the project file (it's an XML file).  You can see it pointing to a .lnk file.

It also presents correctly in the project window, pointing to a .lnk file.

When you double click the .lnk file, LabVIEW correctly resolve the target path, and opens the VI correct, no conflict.

The problem is for the subVIs, somehow the search path fail to be updated.

Should use the target path to search for subVIs, not the path where .lnk file at.

[AristosQueue (NI)]

> LabVIEW shortcut to a VI and its Windows shortcut are same ?!

Noooooo. Shortcut to a VI looks the same to us *users*. If there are two entries in the project tree for the same VI, that's where confusion arises, especially since those secondary VIs may lose the context of their containing qualified names... unless you start annotating with fully qualified names and/or adding additional shortcuts to the owning libraries just to provide context for the VIs.

[Darren]

Any idea that has received less than 7 kudos within 7 years after posting will be automatically declined.