I was working on adding Drag and Drop support for .btm scripts.
This way it is possible to drag one or more files to your script to use the filenames of those as parameters:
One little disadvantage: these filenames are returned as SFN's (short filenames; 8.3 names)
That might very well be caused by the way Take Command is installed on my computers:
It is in fact *not* installed and there is no (usual) association for .btm files.
Before reconfiguring my systems, a question:
Is there anyone courageous enough to report how this behaves on a more default system/ TC installation?
The script to install / remove drag and drop support is straightforward:
The script adds 1 registry key/value pair on install and removes that on uninstall. Should be pretty harmless.
How to?
This way it is possible to drag one or more files to your script to use the filenames of those as parameters:
One little disadvantage: these filenames are returned as SFN's (short filenames; 8.3 names)
That might very well be caused by the way Take Command is installed on my computers:
It is in fact *not* installed and there is no (usual) association for .btm files.
Before reconfiguring my systems, a question:
Is there anyone courageous enough to report how this behaves on a more default system/ TC installation?
The script to install / remove drag and drop support is straightforward:
The script adds 1 registry key/value pair on install and removes that on uninstall. Should be pretty harmless.
How to?
- Create some dummy files (if needed): do var = 1 to 5 (REM>"random filename %var.txt")
- start AddRemoveDragDrop.btm as an admin
- Choose 1
- Drag one or more files to TestParms.btm
TestParms only reports the parameters it was fed.
- start AddRemoveDragDrop.btm as an admin
- Choose 2