Issue changing folders from the Working Files side panel

[dylanvalade]

When I use the dropdown list to select a different recent project/folder the file I'm currently viewing is closed but I must then use the drop down list again to select the folder.

It does not matter what folder I choose for the first click, nothing happens except the open file is closed or at least hidden. The second time I select a recent folder is when Brackets correctly changes folders.

build 0.30.0-9116 (On branch master,master 60dc6b7)

OSX 10.8.4

[njx]

Hmmm. We've had some reports of a similar but possibly related problem, where doing "Open Folder" doesn't work the first time you do it--you have to do it twice. I think I might have run into it myself once but couldn't reproduce it.

If you do Debug > Show Developer Tools, do you see any errors in the console? Also, what extensions do you have installed?

[njx]

Also, what extensions do you have installed? We've had a few that have caused problems with project open.

[njx]

Closing for now. Please reopen if you have any feedback on my questions above.

[PwrSrg]

I was just having the exact same problem (reproducible) which started after installing "Node.JS Simple Application Manager". Problem disappeared after removing the new extension. Here is the error:

Uncaught TypeError: Cannot read property 'file' of null main.js:77
toolbar.actualizar main.js:77
(anonymous function) main.js:90
o.event.dispatch thirdparty.min.js:551
r.handle thirdparty.min.js:551
o.event.trigger thirdparty.min.js:551
o.fn.extend.triggerHandler thirdparty.min.js:551
_clearCurrentDocument /document/DocumentManager.js:508
closeAll /document/DocumentManager.js:569
_loadProject /project/ProjectManager.js:1068
(anonymous function) /project/ProjectManager.js:1408
j thirdparty.min.js:550
k.add thirdparty.min.js:550
openProject /project/ProjectManager.js:1405
(anonymous function) main.js:287
o.event.dispatch thirdparty.min.js:551
r.handle thirdparty.min.js:551

sprint 37 experimental build 0.37.0-12014 (release abbda8d)

[peterflynn]

@PwrSrg Thanks for filing a bug on that extension -- hopefully the extension's author can take it from there.

[BrianCraig]

Yes ,It's my fault !
The problem is in the module that i created.