-
Notifications
You must be signed in to change notification settings - Fork 185
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
Cursor position after adding preset in sequence mode causes an incorrect sequence formation #6272
Labels
Priority: High
Sequence mode
Bucket: Sequence mode related issues
Severity: High
High level visibility to the user
User`s Feedback
Milestone
Comments
svvald
added a commit
that referenced
this issue
Jan 16, 2025
9 tasks
9 tasks
9 tasks
9 tasks
9 tasks
Tested. Bug fixed. 2025-02-11_19h12_41.mp4Desktop:
Ketcher version |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Priority: High
Sequence mode
Bucket: Sequence mode related issues
Severity: High
High level visibility to the user
User`s Feedback
Description:
When adding an RNA preset (e.g., "AUCAU") in Macro mode, the cursor is incorrectly placed between the first nucleotide (e.g., "A") and the "p" (phosphate group). As a result, subsequent additions to the chain are misplaced, causing the RNA sequence to break and leading to an incorrect sequence structure. Ideally, the cursor should always move to the end of the chain after adding a preset.
Steps to Reproduce
Actual behavior
After clicking the first preset, the cursor is placed between the nucleotide (e.g., "A") and the "p" (phosphate group). This placement results in chain breaks and incorrect sequence formation when adding subsequent presets.
Expected behavior
After clicking a preset, the cursor should be positioned at the end of the chain, ensuring that all subsequent additions are appended correctly to form a continuous sequence.
Video
2025-01-14_15h07_26.mp4
Desktop:
Ketcher version
[Version 3.0.0-rc.1]
Indigo version
[Version 1.28.0-rc.1]
#188769167
The text was updated successfully, but these errors were encountered: