CompuServe Messages

#ProWrite Bug?

    28-Feb-92 10:32:20
Sb: #36142-#ProWrite Bug?
Fm: Peter Smithem 71001,3663
To: tom miller 72760,3055
Tom, >> "A Hippy… Coping with the 90's" How about an almost hippy <grin>, I fall into the almost category, almost old enough to go to Woodstock… I HAVE 2.0… The problem is remembering that there is a copy of ProWrite loaded when the "ProWrite Deposit" icon is buried under several open drawers. Several "interruptions" later it's easy to forget what you were doing, "Oh, yeah, I wanted to load xyz.letter, 'click,click'" and you have another copy of ProWrite running. My macro looks for existing instances of ProWrite and puts up a requester "Do you want to run ANOTHER ProWrite", "Yes", "No". Clicking on "No" causes the ProWrite just started to pass the file to the previous instance of ProWrite, then quit. Problem: if the file is in a different directory than the one the first ProWrite was started from, ProWrite can't find the file since there is no way to ask for the pathname of the file it just loaded. This is the case where your macro for loading files (instead of using ProWrite's open requester) doesn't help. Peter