--- In [email protected], "brucexs" <bswit...@...> wrote: > > If you are not using "switch-to-if-active", then I believe that all > PowerPro is doing is using the Windows system routine "ShellExecuteEx" > to run the command line; the hidden parameter is just passed onto this > routine which has an equivalent flag. > > So as best I can tell what you are seeing is some kind of interaction > between the Windows system and tcc (which can sense other instances > and take action based on this as part of startup). > > I am not sure what you are using tcc rather than just running the dev > environment or using Windows start command, but all I can suggest is > either starting a different way or using a PowerPro script to sense if > a tcc instance is running and then doing something different to start. >
I'm using TCC to dig out the last-used project from the registry (via TCC's @REGQUERY[] variable function) so DevEnv will automatically start with that project open. DevEnv itself, and the windows START command can't do that. I'm not using "switch to ...". I tried ShellExecuteEx() in a variety of ways in my own app and could not reproduce this behavior. Here's one anyone can try: when I changed the PowerPro button to use CMD.EXE to open an explorer window: Command: c:\windows\system32\cmd.exe Start: Hidden Parameters: /c start c:\ I observed the same problem ... the hidden instance is created (does its job, exits) and an already-running instance of CMD is also hidden. P.S. I use PowerPro 4.5.02.
