-
Notifications
You must be signed in to change notification settings - Fork 51
Add drag and drop file support #13
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
Open
RatinCN
wants to merge
1
commit into
PlummersSoftwareLLC:main
Choose a base branch
from
RatinCN:drag-drop-support
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When
DragQueryFileAreturns a path thatLoadStartupFilecannot open/read (for example a dropped directory, an unreadable file, or a path truncated byMAX_CMD_PATH),LoadStartupFilesimply returns without replacing the editor contents, but this new path still clearsfDirtyand applies the dropped name as the title. In that scenario the previous buffer remains visible but is now marked clean/renamed, so closing afterward can skip the save prompt for edits that were not actually replaced by the drop.Useful? React with 👍 / 👎.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, this is a valid edge case, but I am going to keep the current behavior for this PR because it matches the existing File > Open path and avoids adding more code size. The existing open flow has the same tradeoff:
(1)
CmdFileOpencallsLoadStartupFileand then unconditionally clearsfDirtyand applies the title(2)
LoadStartupFiledoes not currently report success or failure(3)
PickOpenFilewrites directly intoCmdFile, even clearingCmdFilebefore showing the dialog.Drag/drop can reach a few more bad inputs, such as directories or truncated paths, but fixing that properly would require extra state preservation or a success return path. Since this project prioritizes final binary size over edge-case polish, I prefer to keep this behavior consistent with the existing open logic.