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.

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

Incorrect rendering of Stereo Flags in reactions #58

Closed
Vesdet opened this issue Oct 12, 2020 · 2 comments · Fixed by #563
Closed

Incorrect rendering of Stereo Flags in reactions #58

Vesdet opened this issue Oct 12, 2020 · 2 comments · Fixed by #563

Comments

@Vesdet
Copy link
Contributor

Vesdet commented Oct 12, 2020

Steps to Reproduce:

  1. Create any reaction with multiple reagents and products. Reagents and products should contain Stereo Labels and Stereo Flags.
  2. Click 'Save as' button and save the created reaction in Graph Format.
  3. Open saved in .ket file in Ketcher.

Actual Result:
Reaction_opened
All Stereo Flags were moved to the right top corner.

Expected Result:
StereoFlags_reaction_saved

All Stereo Flags should appear at the right top corner.

Epic link: #56
Relates to: #57

@Vesdet Vesdet added this to the Enhanced Stereochemistry milestone Oct 12, 2020
@AndreiMazol AndreiMazol modified the milestones: Enhanced Stereochemistry, Release 2.3.0 Apr 21, 2021
@Svetlana-Asinovskaia
Copy link
Collaborator

Labels don't render correctly initially if there is a reaction arrow or a reaction plus sign on the canvas.

  1. Create several structures on the canvas.
  2. Add a reaction arrow and the reaction plus signs.
  3. Add several stereobonds to the created structures.

Expected result: Each stereo flag is located next to the added stereobond.
Actual result: Several stereo flags are grouped in one area of the canvas.

bonds

@Svetlana-Asinovskaia
Copy link
Collaborator

Release/2.3 The issue is closed as fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants