-
I would like to know if there is a way create a button to launch multiple tabs? I seem to have no problem launching multiple files. I don't want to create a group and launch that. I have tried to stack the commands on top of each other and prefix them with @async (which works with files), but have had no luck, the tabs just quickly open and I am left with last one in list(pic). The reason I want to do this is so another program can reference the icon that I will drag to the desktop from this button to open the tabs, whether there is a group from them or not.
-
This leads me to the second question (don't know if it would be better as a separate topic). Can the icon that can be created from dragging a button to the desktop be used with relative paths? What I mean is, if it lives in C:\Stuff and references C:\Stuff\MyFolder\MyFiles\test.txt could it always just be (RelativePath)\MyFolder\MyFiles\test.txt? This way I could drag the icon any where and when it is launched it always will load the correct tabs or launch the files I have put in the in the (RelativePath) structure.
Try..
Go C:\ NEWTAB
Go D:\ NEWTAB
..to open multiple.
Regards, AB
Thanks that does the trick for open the tabs I want. Thanks!
I have tried Go {sourcepath}MyFolder\Folder\ NEWTAB and it did strange things. Then I tried just {sourcepath}MyFolder\Folder\ NEWTAB and it worked great, but for only one line if I stack the commands up only the 1st one seems to run.
({sourcepath} shouldn't be needed since relative paths are handled automatically.)
After a line that runs "go" and changes the active folder, any other lines use that folder as a starting point, not the original folder that you started the command in. So the first line will work but the others will be pointing to the wrong place.
You can either make it so that the tabs do not become active (except the last one, which doesn't matter):
Go MyFolder1 NEWTAB=nofocus
Go MyFolder2 NEWTAB=nofocus
Go MyFolder3 NEWTAB
Or you can adjust the paths so that they are relative to what will be the current folder at each stage:
Go MyFolder1 NEWTAB
Go ..\MyFolder2 NEWTAB
Go ..\MyFolder3 NEWTAB
For some reason I keep winding up with the exact path in a different drive letter. I launch it from D:\ but the path I get is N:\MyFolder? I am not seeing any clues for why or where it is grabbing N:\ from.
How are you launching the commands?
Thanks for all the help. I am launching them from a button I dragged to a directory. I think at this point I should say a little about what I am trying to do all this for. I would like have away to include Directories in a database (MS Access). These directories will hold data we don't want in the database because there content may be too big. Directory Opus would be a nice way to go because we can open a combination of Tabs and files all in the *.dcf file. I will develop a way to directly use these *.dcf files and it will send us to the correct directories and open the appropriate files. This is all because I noticed that the *.dcf file is simply just an XML file with some type of Schema(a lot of development possibility there). I have seemed to get it to work perfectly by using what you said with {sourcepath}. When I leave out the {sourcepath} it creates the tab from a random directory I am not even in.
Go {sourcepath}\MyFolder1 NEWTAB=nofocus
Go {sourcepath}\MyFolder2 NEWTAB=nofocus
Go {sourcepath}\MyFolder3 NEWTAB
seems to work great.
What is the "random" directory it goes to without {sourcepath}?
When I double click it in the D:\ drive it was going to N:. For me N:\ is my portable laptop USB drive, it is currently connected to my Desktop too transfer files.
Is Opus running from that USB drive? Or is the dragged-out button file on it?
No, it not in play in any way.
That is strange then. It's possible something has set N:\ to be the current dir in the process that you're double-clicking from within. e.g. Sometimes File-Open dialogs change the current dir if you browse to a folder. (Sometimes badly written shell extensions also change the current dir within their parent process, even though they shouldn't.)