LabVIEW Project - changing target name changes read-only file(s) on disk

[njg]

Scenario: A LabVIEW project containing an FPGA target with supporting files has been created and saved.  All files are set to read-only.

Action: The project is opened and the target name is changed.

Desired result: Nothing on disk changes because everything has been maked as read-only.

Actual result: The LabVIEW FPGA bitfile (*.lvbit) name changes as soon as the target name is changed within the LabVIEW Project.  Note, at this point the project has not yet been saved!

Question: Is there a method for locking projects similar to the "Treat read-only VIs as locked"?

[Doug M]

njg,

This was reported to R&D (# 46IA59LJ) for further investigation.  As a side note, despite the fact that the bitfile name changes, it should still be found by the project and associated with the parent FPGA VI which compiled it.  If you right-click on the FPGA VI and select Target Specific Properties, the path to the compiled bitfile should reflect the bitfile with its name changed.

[njg]

While the bitfile is still associated with the project and the parent FPGA VI that it was compiled from, the main concern here is the effect on source code control software and/or sharing projects among a group of developers.  Granted, the bitfile is not source code and can be regenerated at any time but that process can be very time consuming.  My real request, assuming that it's not already possible, is an option to treat read-only projects as a locked entity.  Thank you for reporting this to R&D.

[Doug M]

njg,

I would highly encourage you to submit feedback on our website for feature requests.  You may want to copy the link to this thread as well. Thanks for the feedback.

Message Edited by Doug M on 02-22-2007 01:37 PM