--- In [email protected], "Raymond J. Ramirez DVM" <r...@...> wrote:
>
> Hello all,
> I have been primarily a lurker, and not as well versed on some of these
> items, so I truly appreciate when you elaborate on your answers, and are
> patient with us users who love the features, yet may not be able to use them
> as intuitively as the rest of you. :-)
>
> So I preface that to ask:
> I understand the relative path/ device number items as summarized below
>
> ***********************************************
> SO TO REITERATE:
> Within PP folder path anywhere: do(pprofolder++"/
> (plus reference to item to launch)
> Somewhere else on the device: do(disk++?":\
> (plus reference to item to launch)
> ********************************
> My situation is my powerpro file is in path
> C:\Documents and Settings\Ray\alldata\powerpro
> on my notebook,
> and as I am playing with some scripts to put on a thumb drive and make it
> portable, the file will only be I(or whichever):\powerpro.
>
> How do I set up something with that? Is that something where I use *exec
> filepath to get the path and use it in a variable so I can use the same
> script for both desktop and portable options?
>
> Thank you in advance.
>
pprofolder is the folder path of the pcf file. It already has a backslash at
the end of it. Powerpro keeps user data in subfolders of pprofolder, e.g.,
Notes, scripts, etc.
file.folder(win.exepath("c=powerpromain"))++?"\" is the folder path of the
PowerPro app folder. It is the same as pprofolder only when the exe file and
the pcf file are in the same folder. Powerpro keeps the plugins folder as a
subfolder of the app folder.
If you wanted the drive's root directory of one of those, you could use the
slice function to get it. For example
win.debug(slice(pprofolder, 3))
returns C:\ on my machine.
do (slice(pprofolder,3))
would run explorer on the root directory of drive housing powerpro pcf file.
To launch a script, as long as the script is located in the scripts folder
under pprofolder, you don't need any folder specs. You just use the command:
.scriptn...@label(anyargs)
where the label and args are only used when the script requires them.
Regards,
Sheri
