orko Posted April 6, 2008 Report Share Posted April 6, 2008 Hey there, I have a project that currently holds template VIs (and their supporting VIs) for use by developers in developing new applications for a system we've been working on. Now I'm trying to wrap this up in the best way possible into a launchable "toolkit chooser" that creates a new project with the chosen template and the supporting (probably in a lvlib) VIs, ready to be saved to any location the developer so choses. I have some kick-off questions, after researching ways to go about this: 1) The Getting Started Window (GSW) seems to be an ideal place to stick the link to the Tk chooser. I've been successful in inserting new items into the LV8.5+ GSW and am pretty comfortable about being able to launch pretty much anything I need to launch from here. For some reason though, inserting a new item in the "new" section pushes the "open" section MRU list down and mangles the "target" dropdown. Does anyone know how to shorten up the MRU area (dynamically would be ideal) so this doesn't happen? 2) Has anyone ever messed around with the "Copy To/From Project" private methods? It looks like they should give me what I need, but I haven't been very successful in using them. 3) Is there any way to programatically invoke that new nifty Project "Save As..." feature so I don't have to "roll my own"? It would be nice to have all the toolkits in their own project files ready to go...and just invoke a Project Save As.... based on their selection so they could chose where to save it and what to name it. 4) Let's say I want the Tk to open up a project from disk (remember, this is from the GSW...so there aren't any active projects open) and programatically pick and chose what I want to copy out of a project on disk into a new project in memory (without saving it yet). I could launch a VI which asks which toolkit to use, then opens up the project on disk, creates a new project in memory and copies stuff over...closing the original project after it is done. Is there any way to ensure that no changes are attempted to be saved to the original project on close? What I mean is, even if I make the template project read-only, there may be a chance that closing it may generate prompts to save changes. I don't want that... 5) Is there a better way to do this? Thanks for any insight! Quote Link to comment
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.