-
Notifications
You must be signed in to change notification settings - Fork 302
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drag and drop for navigation folders, please! #5159
Comments
Definitely! What makes this complicated, is that folders don't really exist: they're parsed from annotation comments in modules, so what we're looking at is something like...
|
A bit involved internal API wise for a "good first issue" I guess |
Would like to be able to drag & drop from one project to another as well... similar to what can be done in Project Explorer, only better: multiple modules instead of one at a time. |
@SmileyFtW good idea! So:
|
ref #3332 |
It would be a "nice to have" to be able to decide if it is a "move" or a "copy" when taking modules to a different project. I would think that more often than not it would be a copy (like PE does), but there might be times when "move" is the desired action (i.e. delete from source after copy to target) |
I think I would make Ctrl+drop be a copy, and standard drag-and-drop be a move. |
I would like to pick this up, but put a restriction on what goes into the feature. I will exclude all the things added to this issue after the initial post. More precisely, the drag and drop will only affect the folder and nothing else. If anybody feels that these should be added, please open a separate issue for things actually copying and moving components in the VBE. |
Justification
When working on a somewhat big project, having the option to drag and drop modules to move them across folders is really a necessity.
Description
I would love to be able to select say two modules from one folder and use the darg and drop feature within the code explorer and move things as needed.
Additional context
When refactoring it is almost certain that modules will make more sense to also change their context in the project's tree.
The text was updated successfully, but these errors were encountered: