Gary Rubin Posted July 17, 2009 Report Share Posted July 17, 2009 Is there any way to add fields (other than just Path) to the Project Explorer? In addition to the obvious additions (e.g. time/date), I would love to see a listing of other parameters, including: Debug on? Preferred Execution System? Priority? Maybe this should go in a Wish List forum? Gary Quote Link to comment
ragglefrock Posted July 17, 2009 Report Share Posted July 17, 2009 Is there any way to add fields (other than just Path) to the Project Explorer? In addition to the obvious additions (e.g. time/date), I would love to see a listing of other parameters, including: Debug on? Preferred Execution System? Priority? Maybe this should go in a Wish List forum? Gary These fields could be bad for load performance if they require the project to load the VI to query them. Currently the project doesn't have to load all VIs that it references, though there are exceptions. If load times get any worse, projects won't be usable at all. Quote Link to comment
Gary Rubin Posted July 17, 2009 Author Report Share Posted July 17, 2009 These fields could be bad for load performance if they require the project to load the VI to query them. Currently the project doesn't have to load all VIs that it references, though there are exceptions. If load times get any worse, projects won't be usable at all. Ah, good point... Quote Link to comment
crelf Posted July 17, 2009 Report Share Posted July 17, 2009 These fields could be bad for load performance if they require the project to load the VI to query them. Only if that information didn't already exist in the project explorer (say, what the status was at last save). Quote Link to comment
Gary Rubin Posted July 18, 2009 Author Report Share Posted July 18, 2009 Only if that information didn't already exist in the project explorer (say, what the status was at last save). I was thinking the same thing on my drive home. I assume a Project is some type of database-like thing. If fields in that database containing additional information for each member VI are updated as each VI is saved, it would probably not slow things down too much. Quote Link to comment
crelf Posted July 18, 2009 Report Share Posted July 18, 2009 I assume a Project is some type of database-like thing. That depends on what you mean by "database" The lvproj file is an XML text file - change the extension to ".xml" (or even ".txt"), open it, and you'll see all the XML tags and thier values. Quote Link to comment
Gary Rubin Posted July 18, 2009 Author Report Share Posted July 18, 2009 That depends on what you mean by "database" The lvproj file is an XML text file - change the extension to ".xml" (or even ".txt"), open it, and you'll see all the XML tags and thier values. Oh, is that all it is? I had assumed it was something more complicated than that. Quote Link to comment
Michael Aivaliotis Posted July 18, 2009 Report Share Posted July 18, 2009 If you use LVOOP (I don't know of any project that doesn't (every VI should be in a class)) then all the VIs are in memory anyway. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.