Recent content by Bernhard S

15.0.4.2064 64-bit is still unusable for me. It takes extremely long to open a larger project. While opening that I get a screen "PL/SQL Developer 64 bit is not responding" When it is finally open and I try to work there I very soon get a screen "PL/SQL Developer 64 has stopped working" => I...

Hello encountered twice today already in version 15.0.3.2059 a screen with: "PL/SQL Developer 64 bit has tstopped working A problem cause4d the program to stop working correctly. Please close the program." With a button: "Close the program" as the only option. How can this be fixed? In general...

So this is stored when "Preferences -> Windows Types -> General -> Save window state" is checked? This was introduced with PL/SQL Developer version 14? How come that changing this checkbox makes no difference in a complete export of preferences? Where is this setting stored then instead?

What causes folders PFinfo and files files.info to be generated? What is the purpose of those system folders and files? There is no explanation to be found in the user's guide.

Another point affecting portability is the file browser setting. See threadhttps://forums.allroundautomations.com/ubb/ubbthreads.php?ubb=showflat&Main=15322&Number=60344 There should be a portable way for that as well.

Hi Marco, could you please add it as an enhancement request to make both, project and desktop files, truly portable and not just the prj files in case when all scripts are in same folder or underneath. Thank you.

This works well for the project .prj file, but not for the .dsk file. In there the whole old path including the drive still appears in sections [Desktop] and [MRU]. Therefore when you open the same project in an environment using a different drive for the project and all project files, no file...

I work on a PC with PL/SQL Developer Project Files (*.prj & *.dsk) stored in a folder on C drive. On a VM (virtual machine) I have the same in a folder named the same, but now on D drive, as C drive there is too small and should therefore only be used for installations. I guess currently there...

Ah, ok. Thank you.

Hi Marco, can you explain, why the path for user.prefs file contains again, even though %APPDATA% is already user specific too?

I really appreciate the possibility to select now multiple files at once in "Files" tab. I can also drag and drop them all at once now then into a project tab or open them all at once via context menu option "Open". Just closing them all at once is still cumbersome. I'm missing a "Close" option...

In "project" tab of "project items" there is a context menu containing among others the following items: Open item Open all Items Close all Items When you have selected a number of items and click on "Open item" it actually opens the selected items. This is a nice feature, just not so...

Thank you. Maybe another option would also be to not create DB-connections for windows exceeding resource limits. Whenever such a window gets activated by the user then, it could automatically or manually reconnect, depending on preferences. I guess a large part of resources is needed just for...

PL/SQL Developer should limit the use of resources itself and stop opening further project windows when it cannot handle those anymore. Opening those anyway and then running into problems makes no sense! It should be possible to open the same project also when there are less system resources...

The project shouldn't be consuming too many resources now when opening this project when it was once created with PL/SQL Developer like that successfully. If PL/SQL Developer reaches windows resource limits it should handle those more properly and stop opening further windows as soon as it's...