--- In [email protected], "Sheri" <sheri...@...> wrote: > > --- In [email protected], "forxtra" <forxtra@> wrote: > > > > --- In [email protected], "Sheri" <sherip99@> wrote: > > > Forxtra, you said about an earlier test version in > > > <http://tech.groups.yahoo.com/group/power-pro/message/35488> > > > > > > > It's working properly without problems at com.unload only at > > > > FIRST time after logon/rebooting. > > > > > > That's what I was experiencing with the latest. I was launching the > > > scripts from an open explorer window (double clicking the scripts). > > > > > > I'm now finding that if I close that explorer window and open a new one > > > for launching the scripts, they do work after restarting Powerpro. At > > > least appears so after a few tries. I have done a few things during this > > > boot, so not 100% sure this the only factor for making it work. > > > > > > Regards, > > > Sheri > > > > > > > I manually set up an association with .powerpro to text editor, > > and I'm usually runnging scripts by user tool on text editor. > > > > Anyway, I tried it on Windows Explorer as you said, but it seems > > to be not effective for me. After restarting Powerpro and opening > > new Windows Explorer, the same problems appear. > > It seems that HOW I browse is also important. If I have opened the Explorer > window from a windows shortcut (and browsed to the folder), the scripts > consistently hang, presumedly at the unload. I can immediately tell Powerpro > is hung, because my script that should alter the fonts when my debug window > opens never runs. > > This is what works: > > After restarting Powerpro, I am using a script that makes a bar. I'm clicking > an entry that runs Menu Explorer. When I get to the folder that holds the > scripts, I right-click the folder entry and select Explore. When I follow > that procedure to open the Explorer window, then double click the scripts, > they run correctly. > > Regards, > Sheri >
You're right. To avoid hanging a PowerPro after restart, the order of executing the program/script or the Parent of a Process seems to be important. Although it's not exactly the same, I could reproduce what you said. I'm using Text Editor as the caller to run powerpro scripts. 1. Restart PowerPro 2. Close the Caller(e.g, Text Editor, File Manager) even if it's already running. then Launch the caller by running powerpro scripts or clicking PowerPro's Bar, not separately. which means PowerPro is the parent process of the caller. 3. Execute scripts containing a call the com plugin within the caller. In the case of WORD and FSO, this way is effective to work properly. Thanks.
