Skip to content
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.

Sign up for GitHub

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

Jump to bottom

"Insert as RDEF array": insert at cursor position #400

Open
humdingerb opened this issue Jun 2, 2024 · 3 comments
Open

"Insert as RDEF array": insert at cursor position #400

humdingerb opened this issue Jun 2, 2024 · 3 comments
Assignees
@jackburton79

Comments

@humdingerb
Copy link
Contributor

Currently the new array gets added to the end of the file. If the user wants to have their resources in some order, this means copy&pasting stuff around. It'd be easier and intuitive to insert the data at the cursor position.
@jackburton79
Copy link
Collaborator

While I somewhat agree with you, initially it worked like this, but it could be a problem if the cursor is placed inside another resource.
We'll leave the function as is in the 3.0 release. Let's gather some other feedback before changing it.

@humdingerb
Copy link
Contributor Author

Right, that might be an issue...

Maybe the file could be scrolled to the end, where the new resource was appended, and the new block being selected? Then one could at least cut&paste it directly where it should go.

jackburton79 added a commit that referenced this issue Oct 23, 2024
@jackburton79
When importing a RDEF resource, go to the end of the file
5498a63 
Since the RDEFs are appended to the end of the file, at least move the caret there so the user
sees something. (#400)
Would be nice to also select the newly appended text, maybe.
@jackburton79
Copy link
Collaborator

Now we at least scroll to the bottom of the file.
Selecting the whole text might be a bit more complex, especially since we could add more resources in a row

@jackburton79 jackburton79 self-assigned this Oct 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jackburton79 jackburton79

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jackburton79 @humdingerb