ProWrite Bug?
Tom,
ProWrite runs the "ProWrite Startup" macro if it finds it in the drawer
containing ProWrite. I played around with hard links to ProWrite a little
and it will load the ProWrite Startup macro from the directory containing
the link (I've been using this to let me change some things at startup
depending on the files I'm working with), but unfortunately it seems to
grab the "ProWrite FKeys" file from (and save any changes to) the directory
containing the real copy of ProWrite. It expects the actual macros to be in
the directory ProWrite was launched from via the hard link (the dir
containing the link). If you can keep track of what the macros actually do
with all the same names in the list, you can have a different set in each
directory containing a link (fun keeping track of it all though, some of
mine are links to a common directory and others are macros specific to the
files in the current dir. but they all have the same names).
I have this nasty habit of loading existing files by double clicking on the
file icon (so does my wife, which is one of the things I use "ProWrite
Startup" for, for some strange reason my Amiga starts running low on memory
after she loads up 15 or 20 copies of ProWrite ;^).
I'll have to try loading files via macros so I can keep the pathnames
somewhere. I must have missed the upload of RexxArpLib.library 3.0, my copy
is 2.5, I'll look around for it (wish Whap! wasn't acting up, I hate
downloading manually).
Peter