I started up the current release of Dev-PHP IDE v2.x and clicked on the "Open" icon at the top. The program did not open and instead I got the following dialog box. To be fair though - the program was in the "Files" list on the right and I could click on the name and the file would then show. Otherwise, the screen was blank in the editor with the name of the file on the left.
Thank you for spending time describing such a frustrating bug and finding a workaround.
I will try to reproduce the problem.
New version supposed to fix that stuff.
2.7.6.38 (Options > Check before update - then click on the "Exp" version).
While it is true the program no longer has an error message - the PHP script still does not show on the screen. Now, however, the file is not even showing up in the Files tab on the left. I'm trying to open a simple PHP script that only has "". I'm going to try making an HTML file with this in it. Made test.html. Although I can select the file - it is not loaded in to the editor. I found out, by trying various menu commands, that the File->Recently Used->[Pick a File] will now display the file. But whereas before the file was put in to the Files area on the left - that no longer works.
Sorry about that. I can’t reproduce this bug. It must be depending on a specific data context...
May I suggest you uninstall Dev-PHP and install the latest full version (it comes with a mini "project": a tree-structure composed of two small files)?
I was able to reproduce (and fix) several bugs appearing at startup, particularly when dropping file(s) on the Dev-PHP icon - whether Dev-PHP is already running, or not.
Let me try the latest release. If the problem persists BRB.
Ummmmm....still getting bad results. Now, when I try to use File->Open I get this:!
Maybe clumsy...
a) You must download the latest version (according to sourceforge, nobody did download it yet)
https://master.dl.sourceforge.net/project/devphp/Dev-PHP%202.0%20IDE/2.7/devphp2_7_8_38.exe
b) Then install it and "force" application data as below:
Nota: At the moment, I am unable to reproduce this bug (although I fix some other related ones).