[Fwd: Launching multiple copies of DAG-Edit from Mac OS]

[Pankaj Jaiswal]

Just FYI. I will add this to the docs.
Pankaj

-------- Original Message --------
From: John Richter <john.richter at aya.yale.edu>
Subject: Launching multiple copies of DAG-Edit from Mac OS
To: Felipe Zapata <fzqhd at studentmail.umsl.edu>
CC: Pankaj Jaiswal <pj37 at cornell.edu>


Hello, Felipe. I've done some research into launching multiple instances of
DAG-Edit on Mac OS.

It turns out that the problem is not DAG-Edit, it is the way the Mac OS Finder
wants to treat java applications. The finder sees that DAG-Edit is already
running, and just never sends DAG-Edit the signal to start up.

However, I think I have a solution that will trick Mac OS...

I've created a Mac OS Application (actually a compiled AppleScript) called
"macos_multilauncher" which I've attached to this email.

Put the macos_multilauncher file into the folder where you installed DAG-Edit
(probably Applications:DAG-Edit). Once you've done that, double-clicking the
macos_multilauncher should cause DAG-Edit to start up. The
macos_multilauncher should be able to start up as many copies of DAG-Edit as
you want. Also, you can drop the macos_multilauncher onto the Mac OS Dock,
and it should still work properly.

Some notes:
---------------
* You have to put macos_multilauncher into your DAG-Edit installation
directory! If you put it anywhere else, it won't know how to find DAG-Edit,
and it won't work.

* Because of the way macos_multilauncher starts DAG-Edit, DAG-Edit will NOT
generate the .dagedit.stderr and .dagedit.stdout files used for debugging. So
if you encounter a bug while using the macos_multilauncher, you will have no
way of sending me the details of your problem.

* The preferred way to launch multiple instances of DAG-Edit is to launch the
first instance using the normal DAG-Edit shortcut, and then launch additional
instances using macos_multilauncher. That way, at least one of the DAG-Edit
instances will be correctly writing out debugging information.

* All the instances of DAG-Edit you run will share a single configuration
file. This means that DAG-Edit will remember your preferences FOR ONLY ONE of
the DAG-Edit instances you are running, and there's no way to be sure which
instance of DAG-Edit will actually store it's preferences. So, if you are
wanting to set up DAG-Edit preferences, or create file loading profiles, or
something like that, run only one instance of DAG-Edit.

Let me know of the macos_multilauncher file works for you. If it does, I'll
start including it in the standard Mac OS installer for DAG-Edit.

	-John


-------------- next part --------------
A non-text attachment was scrubbed...
Name: macos_multilauncher
Type: application/octet-stream
Size: 13780 bytes
Desc: not available
URL: <http://brie4.cshl.edu/pipermail/po-dev/attachments/20031104/85ba60b9/attachment.obj>