relaunch anomaly

Mark Schonewille m.schonewille at
Fri Feb 26 03:33:28 EST 2010

Hi Paul,

This script might help you: (mind line wraps on the  

Since it is now possible to sun VBScript woth the do command, you  
might take the script apart and only use

   put tVBS & cr & "WshShell.AppActivate" && pTitleOrID into tVBS


   put tVBS & cr & "WshShell.AppActivate" && quote & pTitleOrID &  
quote into tVBS

Best regards,

Mark Schonewille

Economy-x-Talk Consulting and Software Engineering

Economy-x-Talk is always looking for new software development  
projects. Feel free to contact me for a quote.

Op 26 feb 2010, om 06:16 heeft Paul D. DeRocco het volgende geschreven:

> The docs say that not passing the relaunch event, and not returning  
> anything
> from the event, causes the new instance to terminate and the old  
> instance to
> become the foreground window. When I do this under WinXP, everything  
> works
> as advertised, including passing the command line parameter to the old
> instance so that it opens the appropriate document file, except that  
> the
> window remains in the background. Is this something that varies with  
> OS
> version? Is there some Revolution command to force the old instance to
> become the foreground window anyway?
> --
> Ciao,               Paul D. DeRocco
> Paul                mailto:pderocco at

More information about the Use-livecode mailing list