#ProWrite Bug?
V.36177
Pete,
Not sure exactly what you were getting at in your last post. Looks like
you touched upon three different things and in the process uncovered a few
more short comings of Pro Write.
Lets talk about the last thing you mentioned under the heading "Problem:".
My macro (using the rexxarplib) does not load a file into Pro Write. It
sends the full path name of the file you selected to rexx. It is up to
rexx to load that file into Pro Write, but rexx now has the full path name
of that file, to do with as you will, and that was what you wanted. You
don't have to ask Pro Write for the file path, you already have it!
"ProWrite Deposit" ——- Icons that were generated by Pro Write have no
trouble when they are placed into the Deposit. They DO NOT open a second
copy of Pro Write, they appear in the existing program just fine. It makes
no difference were on your system they are located. BUT files that never
have been through Pro Write will not load. Pro Write can not find where
they are. (see last paragraph)
Double clicking or Shift clicking file icons WILL open a second or third
copy of Pro Write. Now, Pro Write knows when it opens a second copy,
because it renames it's port with an extension that, not only reflects that
more then one copy is running, but names which copy it is. So it knows
that you are asking for the third or tenth copy of itself. (will be tied
in).
Shift clicking an icon with Pro Write will cause it (the file) to load. Pro
Write must get the path info from the OS. SO……………
It looks like any icon dropped into the deposit or shift clicked on or a
Pro Write file that's double clicked on should A) generate a requester to
see if a second copy of Pro Write should be opened. B) Use the OS to find
the path to load the file. Since this is not the case; I think we have a
short coming, not a bug or miscoding, but some thing that does not work
quite right and some thing that can easily be fix. Pro Write if your
reading add this to the list of things to be looked into. O.K.?
-Tom