-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Cannot create new file in the project root once you create new files in a folder. #9341
Comments
This exact same behavior occurs in Release 0.43. The reason this happens is that
So, it falls through to the third case and creates a file next to the one you're viewing. I think we should change this, but it would represent a change to the API. I realize that the above already represents a change to the API because the idea of a "context" item did not exist before. My suggestion is that the third case should be to default to the project directory rather than the currently viewed file. If you're right clicking in the open area in the tree, that seems like a reasonable default behavior. What do you think, @peterflynn? |
Tentatively leaving the release 0.44 marker on this thinking that we may want to make this change, though this issue is not a regression from 0.43. |
We reviewed this earlier and decided that it's not a release blocker. The fix is simple and I think a reasonable change to |
This turns out to be a bit more complicated and I don't know that we should try to fix this for 0.44. The issue is that if the Working Set has the focus, then I have a branch which implements this behavior change and makes opening the context menu on the file tree shift focus there. I'm not fully happy with how that works now because it can leave you in a "nothing has the selection bar" state. |
De-assigning myself because I'm not actively working on this now. |
Any update on this ? It's annoying for both files and folder. Though with folders you have workaround by opening the lowest folder first, for root files there is no solution. |
Same problem for me while trying to create a new file in the root folder. |
It's not obvious, but a workaround is to right-click on any file (not folder) in root, then New File and New Folder will create new items in the root. |
Result: the new file/folder is created inside the first folder created in step 2.
The text was updated successfully, but these errors were encountered: