Attempting to change project when there are unsaved files makes Brackets unresponsive
I work with big projects and this plugin helps a lot when changing between them. Thing is, I have to remember to save all files before changing or else 1- It won't change to the other project 2- The editing window becomes unclickable and I can't modify anything. The open projects button disables too.
Was this the expected result?
It would be great to have a prompt to save the files before changing or something like that. If I find some time I'll try to add it myself.
Brackets v1.4
Thanks for report! Could you please provide the error in development tools if you see them ?
Also, as quick solution you can have an extension that will autosave your files when you switch to another file (I have installed such extension a long ago and maybe this is a case why I didn't see that issue).
Yeah, I opened devtools and there is no error, other than: Failed to load resource: the server responded with a status of 503 (Service Temporarily Unavailable) http://online-dnbard.rhcloud.com/tick/542ba89acfe5e6c4c60000e2/71ee7f0e4e728891ad5ad5d00c249e72
By the way, what is that? I get that error when I run Brackets, everytime, but everything works perfectly.
Anyway, when I "crash" the plugin it doesn't show any error, it just doesn't let me do anything except displaying the options in the menu bar.
- This is the anonymous statistics server.
- I'm going to stop using it from the next version of this extension.
Regarding the issue: will try to reproduce it myself.
Also happens to me. If it helps, here are the steps to reproduce:
- Open a project.
- Open a file.
- Make some changes but do not save the file.
- Press alt+p to open the projects modal.
Expected outcome: 5. Brackets should ask if I want to save or discard changes. 6. After the choice is made, the projects modal should pop up.
Actual outcome: 5. Projects modal opens. 6. Choose a project. 7. Projects modal closes, but no changes can be made to files open and menus work erratically. Refreshing or restarting Brackets solves the issue.
As @rolivav commented, there are no errors in the developer's console.
Exactly what @xtoq describes.