Jacqueline,
thanks for your answer. No, leaving the quotes off makes
no difference, the application is launched, it is visible in the
task manager but it is not visible on screen.
I tried hard to figure out what is the reason for this behavior, but
I didn't find any answer yet.
Ralf
On 07.04.2008, at 06:04, J. Landman Gay wrote:
Ralf Bitter wrote:
Does anyone know under what circumstances the launch command
launches an application in an invisible state?
Is there a Windows shell command to make the launched application
visible again?
I have a windows standalone (runs on XP) with a launch command like:
put "C:/folder/folder/folder/folder/myApplication.exe" into tAppPath
do "launch" && quote & tAppPath & quote
This launches the application, but it is not visible. I can see the
entry in the task manager.
There is no problem with the Mac standalone.
Did a quick test with another standalone, which does nothing but
launch the said application.
It uses the same handler and it works as expected.
So, this must have to do with something specific to my standalone.
This is in version 2.8.1. Any idea, anyone?
Does it work if you leave off the quotes? For example:
launch tAppPath
The variable is automatically treated as though it is quoted, so you
don't need the extra ones. I don't really think that's the problem
but it is easy to try.
I'm interested in knowing if you figure this out. Someone wrote to
tech support and said the launch command wasn't working, but after
seeing your post I wonder if it is launching invisibly instead. He
is running XP like you are.
--
Jacqueline Landman Gay | [EMAIL PROTECTED]
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
