What's wrong about using FileLocator? I am a late-bound reference. I refer to a file or directory in relation to a well-known location on the filesystem, called an origin. When asked to perform concrete operation, I look up the current location of my origin, and resolve my path against it. Usage ---------- FileLocator vmDirectory parent pathString
'/Applications'
FileLocator desktop. FileLocator desktop basename. FileLocator home basename. FileLocator image. FileLocator vmBinary asAbsolute pathString
'/Applications/CogVM.app/Contents/MacOS/CogVM' FileLocator vmBinary pathString '/Applications/CogVM.app/Contents/MacOS/CogVM'
On Wed, Dec 2, 2015 at 11:51 AM, Ferlicot D. Cyril <cyril.ferlicot@gmail.com
wrote:
Le 02/12/2015 11:35, Dimitris Chloupis a écrit :
I have a startup script that loads the libraries and project I mostly use, including my own, but I want that script to target specific folders and its subfolders , is this possible ?
Hi,
You can use "FileSystem workingDirectory" to get the directory of the image. Then you can use some condition to execute or not a block that contains your startup script.
-- Cyril Ferlicot
165 Avenue Bretagne Lille 59000 France