Re: Portable XY
- From: Fred Weiner <fw1948@xxxxxxxxx>
- To: xywrite@xxxxxxxxxxxxx
- Date: Mon, 25 Jun 2012 08:20:03 -0700
On Mon, Jun 25, 2012 at 7:45 AM, Carl Distefano <cld@xxxxxxxxxx> wrote:
> <VA$ED> includes both the path and the EXEcutable's filename; if you use
> <VA$ED> you must parse out the filename.
Clear. No need to add the extra step. Next question: how to make
SETTINGS.DFL portable? Of course, one could remove all instances where a
path is hard coded and invoke them in STARTUP.INT. But for my learning's
sake, will the settings file allow for the same VA usage? FW.
Other related posts:
