Uh, well, yes Don; I guess I need to clarify.
I don't want to run more than one instance of Studio. However, I want the already active Studio to accept the incoming request and not bail out because it is already loaded/locked...which requires me to terminate Studio just so it can immediately be restarted. This is inefficient, particularly bc of the longish Studio init time required upon startup.
In other words, I want it to behave like my other apps do. eg SNS-HDR.
SNS-HDR, if running stand-alone, does not bail when called because it is already running...instead, it says "ok, give me what you got" and proceeds as expected. That doesn't start another instance; it uses the one already running.
Firefox and many other apps are able to recognize that they are already running and act accordingly; they don't bail when the n-th remote url is clicked on from a calling app because they are already loaded/running.
Are you saying that future Studio can't be coded to do the same? (I know it doesn't have that behavior now)