Fix for 3876 - Dropping Leo Outline File Fails #3881
Conversation
This file contains 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
…n helper functions. Fixes Issue leo-editor#3876
|
That second commit was just merging my branch to update it with the current devel branch. |
… to insert file contents. qt_frame.py - refactor logic for redability and simplicity.
|
This 3rd commit fixes the failure to insert the external file's body for non-Leo files, using ekr's suggested code change. This PR is ready to merge. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR fixes the problem that drag-and-drop of a Leo outline fails.
This PR is a work in progress because drag-and-drop for non-Leo files creates empty nodes instead of populated trees for non-Leo files.
See #3876.