Limit to one instance

[Rahul P]

Hi,

Is there a way you can limit the PL/SQL developer to one instance only?

Here is my reason. We have a source control called Mercurial. In it's setting, I put the default viewer for the package files to be pl/sql developer. So, when I open the file from Mercurial, it fires up a *new* instance of pl/sql developer, which is not ideal. I would like to know if there is a setting or a command line parameter I can invoke to force it to open the file using the instance that is already running.

Thank you,
Rahul.

 

[Marco Kalter]

As a test: what happens if you start PL/SQL Developer and double-click a source file in the Windows Explorer? Does it open in the same PL/SQL Developer instance or in a new one?

 

[Rahul P]

Opened a new instance using Windows Explorer also.

 

[Marco Kalter]

Okay. Can you go to Tools > Preferences > Files / Extensions, press the "Register Filetypes" button, select the appropriate extensions, and press "OK". Exit PL/SQL Developer, reboot the PC, and check if this helps.

 

[Claus Pedersen]

I am having the same problem and it's quite irritating. I think it is Windows who decides if a program should be spawned in a new instance when double-clicking a file. To me, it seems random which programs will open files in the same instance and which will spawn a new instance.

A work-around for PL/SQL developer: use copy-paste

Copy your file with Ctrl-C
Make PLD active with Alt-tab
Copy the file into PLD with Ctrl-V

This will open the file in the same instance just as if it was opened from the File-Open menu or drag-and-dropped.

 

[chepworth]

I have had this frustration as well. However, drag and drop also works to open a file from explorer into the same PSD window. It is hardly ideal, but it becomes habit after a while.