PhpED 5.0.1 (5028) loses custom window layout, and file->exit does not exit PhpED application!


The following sequence illustrates the problem:

1. I have a PhpED project and workspace open, and I setup the following layout,


code explorer window on left,
and along the bottom of the screen I have:
explorer [1] window, which has workspace and explorer tabs
explorer [2] window , created with view->clone window->explorer command, then docked
call stack window,
log window, with errors, log, transfers, globals tabs.

2. I then exit PhpED.

3. I restart PhpED, the workspace is loaded automatically, and all is well.

4. When I try to exit this phped session, clicking on file->exit, or the window close X
just results in the workspace closing, and the explorer[2] window dissapearing.

5. I have to do file->exit a 2nd time to make the PhpED application actually close!

6. When I then re-start phped, no workspace is loaded.

7. I can then use file->open workspace to reopen the workspace, but the explorer[2]
window is not restored.

If I then go back to step 1, and re-create the explorer[2] window the same sequenc repeats.
ie the session where I setup the layout exits normally, and the subsequent session starts correctly.
But when I try to exit from that session, file->exit does not exit the application.


PhpEd 4.x didnt have this problem. I didn't try 5.0.0.0.

If I got you right, no problem happens when you work with default lauout or with layout dropped to defaults with View->Restore default layout.
So it happens only with your custom layout. Right?
Honestly we did not get any reports like this and I'd highly appreciate if you provide us with layout.cfg file produced by the IDE right after the first run and screenshots of the windows how they look like on your machine.

Yes I've just cheked, it only happens with custom layout.

How do I send you the sceen shot and layout files ?

You've already contacted support by email. Please proceed.

I Recieved a fixed version today.

Congratulations to NuSphere for super quick response.

Thanks for your report.
Fix is included in build 5029 which is avalable online since Aug 9 (today)