Summary - Creo Leaves Command Prompt Window Open

[dgschaefer]

Thanks to Ben for digging up a thread from this summer with the answer.
I vaguely remember it now, but Creo wasn't on my radar back in June so
it didn't stick.



My batch file has this now:



call "%proe_executable_folder%%proe_executable%"



It needs to be changed to:



start "Creo 1.0 Parametric" "%proe_executable_folder%%proe_executable%"



You need both parts of the 'start' statement, the descriptive bit after
'start' and the full path to the executable. I tested it and it does
work with Creo. Unfortunately, since my batch file launches WF3, WF4 &
WF5 too, I've got to figure out how to make that 'start' statement work
with them too. Creo already added 2-3 new variables to my script
because the text folder and the bin folder aren't in the same parent
folder anymore and Creo installs in a folder with the build code. Guess
I'll need one for the description too.



Thanks,



Doug Schaefer

This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

[dgschaefer]

I sent the summary too soon. Turns out the description doesn't matter
at all, just as long as there's something there. So this:



start "Creo 1.0 Parametric" "%proe_executable_folder%%proe_executable%"



works just as well as this:



start " "%proe_executable_folder%%proe_executable%"



And the latter works fine with WF3, WF4 and WF5 too.



Doug Schaefer