Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 6 subscribers
  • Views 1060 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How can i run another Instance of an Application by Double Clicking on its Application Icon

ankitverma05

How can i run another instance of the application  while the application is already running, by clicking on the application Icon in /Applications/.
I dont want to run it from /Applications/myapp.app/Contents/MacOS/myapp

Can i link a script file containing statements
(1)open -n /Applications/myapp.app
or
(2)open -n /Applications/myapp.app/Contents/MacOS/myapp

with the application icon click....

i have tried making changes in Info.plist of the application
key-Executable file    value-myapp    {present at /Applications/myapp.app/Contents/MacOS/myapp}

changes
key-Executable file   value-launch.sh  {present at /Applications/myapp.app/Contents/MacOS/launch.sh}

As i know an  Application Bundle on OS X  can only be started once.by simply copying the bundle the same application can be launched twice.

Is there any solution for the above problem

Thanks
Ankit

:1010172


This thread was automatically locked due to age.
Parents
  • 0

    Not really the correct forum for such a question, but something that's doable.

    Historically, unlike Windows Explorer, the Finder will only launch an executable binary once... a second launch attempt will bring it to the front.

    Platypus is my tool of choice for making launcher wrappers to bypass this -- you could try a few different things, such as making an applescript droplet that links a script as you describe when you drop an application on it, or create a folder action script that runs the application with -n when some action happens within that folder.  Or, you can just wrap the entire bundle inside a platypus application that runs the script you indicate below, for standard double-click multiple execution, from inside the meta-bundle.

    So, there are many solutions to the issue, depending on what you want to do.

    What I personally usually end up doing is command-D, followed by launching the copy.  This only works of course if you donl't care about overwritten plist files -- which is one of the reasons app bundles don't multilaunch in the first place.

    :1010258
Reply
  • 0

    Not really the correct forum for such a question, but something that's doable.

    Historically, unlike Windows Explorer, the Finder will only launch an executable binary once... a second launch attempt will bring it to the front.

    Platypus is my tool of choice for making launcher wrappers to bypass this -- you could try a few different things, such as making an applescript droplet that links a script as you describe when you drop an application on it, or create a folder action script that runs the application with -n when some action happens within that folder.  Or, you can just wrap the entire bundle inside a platypus application that runs the script you indicate below, for standard double-click multiple execution, from inside the meta-bundle.

    So, there are many solutions to the issue, depending on what you want to do.

    What I personally usually end up doing is command-D, followed by launching the copy.  This only works of course if you donl't care about overwritten plist files -- which is one of the reasons app bundles don't multilaunch in the first place.

    :1010258
Children
No Data