on systems where DLC is not defined as an environment variable (normally windows), is there any way from the ABL of determining where DLC is installed ?
This has to be for tty, webspeed and GUI, windows and client.
I was looking for session:DLC or session:install-dir but of course they don't exist. That would be too easy.
Thanks
The trailing entries on the PROPATH?
ahhh. Now, I can't use that either.
I use the -baseADE startup parameter to automatically add all .pl in
the folder specified to the propath. I then want to add the standard
.pl files by switching session:base-ade to the progress directory
(tty/gui) which then automatically adds all .pl's in that directory to
the propath
On 16 December 2011 22:18, Thomas Mercer-Hursh
GET-KEY-VALUE?
Or OE11?
System.Environment:CommandLine
returns the path to the current executable, just remove bin/_progres.exe, bin/prowin32.exe, bin/_proapsv.exe, etc. and you have $DLC
GET-KEY-VALUE is not supported by "speedscript". Or so it says in the manual
System.Environment:CommandLine is not available in linux
Julian
On 16 December 2011 22:30, Mike Fechner
System.Environment:CommandLine is not available in linux
But there you can use the DLC from the OS environment variable, or? I understood your question so that you need a solution for Windows.
So you'll need to differentiate based on OPSYS
true.
Linux isn't a problem. I'm blinded by trying to find a one-size-fits all .
Thanks for removing the blinkers.
Now that 11 is out, I will use the .net version
On 16 December 2011 22:38, Mike Fechner