B.Wettengel Posts: 23 30/06/2015

B.Wettengel Posts: 23 Hello Gianluca, It would be helpful (at least for some of my use cases) if you get the full path where SyMenu is located. So I suggest to - add another Universal Unit Identifier (e.g. #~:\ ) which will be substituted with the full path of SyMenu, not only the Drive-portion where SyMenu is located. Why: In portable scenarios you probably know the relative path to SyMenu, but not the portion in front of it. If you need the full path to an object you are not able to specify it. E.g. SyMenu is located on F:\..AnyFolder..\SyMenu. Assume you have programs located in F:\..AnyFolder..\SyMenu\ProgramFiles\another_prog.exe and you need the path for this program. You can not specify #:\\SyMenu\ProgramFiles\another_file.ini, because you don’t know then name of ..AnyFolder.. and therefore will not work. (Especially in network-locations, when different people are involved) If you had the full path to SyMenu (e.g. #::\) you are able to write #~:\\SyMenu\ProgramFiles\another_file.ini and this will resolve to F:\..AnyFolder..\SyMenu \ProgramFiles\another_file.ini Note: Sometimes you can overcome this situation by defining Workdirectory, but this doesn’t work on Networkshares with cmd.exe (the workdirectory will be set to c:\windows by cmd.exe!) What's your opinion? Greets Andreas

link

---