highend wrote:tab("new", <location>)Does that one really allow <drive name>|<path>?
Probably not (from my testing) hence the wish. I figured I'd try it because you had %drive% in your post (example), but I guess you're not doing that. Maybe it will if we get our wish.
I haven't toyed with the USBDLM variables (e.g., VolumeLabel) much yet. It would be nice if they could carry over into the outside environment. I added this line referred to in help to the ini file, but I may have to reboot to see if they made it to the Windows environment.
Code: Select all
"From the help: These variables can also be made available as environment variables for processes started by USBDLM.
Which variables are required must be configured"
UsbdlmVariablesToOpenEnvironment=DevName, VolumeLabel
So, I think this means we can use these variable in the "open" line in USBDLM such as a command line parameter but not in the XY script itself.
Anyway, I got the inserting of a flash drive to work fine (i.e., new tab made with the drivename as the caption) invoked via USBDLM [OnArrival10]. I haven't had enough time to solve my issue with installing additional drives (i.e., prevent a second new tab from being made for the initial drive when installing the second drive).
The script for removing the drive (using removedrive.exe) and the associated tab also works, but currently that script is being started by pressing a CTB/menu (which is fine with me). However, I have to resolve what happens if I don't eject the drive via a CTB/XYplorer script. For example if I simply eject the drive from the tray, there wouldn't be any need to remove a tab if I wasn't using XYplorer or XY wasn't running. Though I might want to remove an XY tab if XY was running but not "active" and the drive eject was invoked down in the tray. In that situation the script could be invoked via [OnRemoval1] in USBDLM. As you well know, it can be a bit bit confusing depending on how the drive is ejected.
Thanks,
Ken