ProWrite questions
6 messages in this thread
Is there any way for an ARexx script to get the full pathname of the file
being edited? The DocName command doesn't return the full path of the
document. I have been printing mostly in "High" quality and it takes quite
a while to print multi-page documents. I'd like to write a macro to pass
the file to another copy of ProWrite and tell it to print the file while I
continue editing other files.
It would be nice if the print routines were a separate process so that
ProWrite wouldn't be hung up during a long print job (a spooler doesn't
help here since all the time is consumed by ProWrite rendering the
document).
Also, I reported a bug a couple of weeks ago where ProWrite crashes when
another application closes the WB. Has any progress been made with this? Is
there any hope for a patch in the near future? It is painful (and hard to
remember) to keep exiting ProWrite any time I need to run an application
which closes the WB.
Peter
Peter,
Right now there is no way to get the path full path of a document in a
macro. The only thing that I think you could do at this point is hard-code
a path into your macros.
That bug has been stomped on. We are still in testing on that version.
I'll notify everyone on here when testing is complete and we have a version
for you.
Mark
New Horizons Software, Inc.
Hard coding the path to the files in the macro is not useful since my
documents are organized into several different directories. According to
the docs, there can be only one "ProWrite FKeys" file in the same drawer as
ProWrite, so I cannot have macro files for each working directory (this
would be a nice feature). I tried getting around this by making a hard link
in my working directory to the copy of ProWrite in my editors drawer, but
this arrangement caused ProWrite to crash while loading. It's possible that
I messed up creating the link and I'll try this again when I get a chance.
Are there any files that MUST exist for ProWrite to start up? I can copy or
link them into the working directory if so.
Peter
Another vote for document windows revealing their full paths when asked.
Bob
ProWrite needs no file to run, except itself, of course. Links do
have some side-effects that might cause you problems. I'm not sure
how this will affect your opreration, but when a program gets a lock
on a link, that lock is on the original object, and not the linked
object. One problem that this causes is that when you run a program
from the Workbench, the Workbench passes WBArgs to the running
program. The WBArgs contain information such as from where the
program was run (by a lock), and locks on all the icons that were
selected when the program was run. But anyway, this is technical and
I don't think I should go into it any further. Let me just say that
there could be problems and you will just have to experiment.
Mark,
The technical stuff helps to understand what's going on (I have not gotten
the 2.0 Tech Refs yet). I'd still like to see the Arexx interface enhanced
a bit.
Peter