--- In [email protected], "brucexs" <[EMAIL PROTECTED]> wrote: > > > > > > > > The script itsself is stored in a file, but I call it from the > hooks > > list. > > Right, so a script in memory is executing (and calling a script in a > file, but it is still running till that file script returns). > > > >> Also, pressing apply doesn't crash it. > > I think reason is due to the sequence of events as follows: > 1. Press OK on pproconf. > 2. Config window is closed. > 3. windows system sends message to powerpro that window event has > happened and hook script starts > 4. config program finishes processing ok button and sends message to > powerpro.exe to restart with new pcf file. This happens while in- > memory script starting in 3 is still running > 5. Crash. > > For apply, the config window is not closed, so 3-5 do not happen. > > ONe can think of possible ways to work around this, but they either > involve redesigns of config (do step 4 before 2 in above) or chance > of other timing errors. I have not plans to try them for now. > > > > > > > Your workaround seems to be fine, is there a way to make the config > > dialog start with a specific command list selected though? Like > when > > you click on configure in command list context menu. > > following on one line > > start /wait "" "c:/program files/powerpro/pproconf.exe" ? > commandlists "?clistname" > > You'd have to pass clistname to batch file as parameter if it varied. > > > >
Works great :) Just wondering, couldn't you disable the hooks for a moment before closing the config? Then it wouldn't process the closing of the dialog.
