having two current paths

[wiebe@CARYA]

Here's another one. It has to be duplicate (at times it is so anoying), I can't find it though. If it is, please someone explain to me how to better find these duplicates.

Let's say you are editing your program. So you work in your project directory. Insert VI, Open, etc all start where you have been working recently.

Now you run your program, and select a path for your file (not a VI). You want these files to go somewhere else. You need to browse.

Then you start editting again. You have to browse all the way back to your project.

Then you start testing again. You have to browse all the way back to your data folder.

Then you start editting again. You have to browse all the way back to your project.

Then you start testing again. You have to browse all the way back to your data folder.

Etc.

I know. I can work around it. Create short cuts or something.

How about keeping a current path for edit time, and one for running time?

Regards,

Wiebe.

[AristosQueue (NI)]

It's a good idea. We'd have to figure out how to handle all the editing tools that are part of LabVIEW that are running VIs, but I bet there's a solution for that.

[rolfk]

I solve this by having one (or more) application configurable and maintained current directory variables. All the File dialogs in the application get invoked with the according current directory as start path, and the current directory MIGHT get updated after the dialog invocation returned successfully with a selected file or directory.

The LabVIEW current directory separation for runtime and edit time might help for simple projects but it will not be enough for more complex applications where you have usually more than one kind of working directory for different types of files.

[wiebe@CARYA]

In my applications, I also often do maintain a lists of appropriate paths for dialogs. But that still ruins the path LabVIEW uses during edit time. So in my application, I can control this, but when my code stops, the most recent path was still changed to my applications last directory, and not pointing to my code anymore. I don't have control over that (well maybe through a dll or ini key). It's very likely my application paths the path used during editing are completely unrelated. QD and the project explorer made this a less occasional annoyance.