-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Allow change of length in bond properties #9
Comments
During the drawing process, the atom label characters are positioned first such that the area occupied by the string of each of its characters (excluding any implicit H or charge characters) is centred on the atom's position. In the diagram below the atom's position is shown as a red dot and the bounding area of the elements characters is shown in orange. I hope this helps you to see why when the bonds are the same length that the rendered bond may be different. |
@deadlyvices Can you think of what would cause the bond length snapping not set the length to 50 in case of the structure @tomyan112 has drawn? |
No idea at all. You can drag the bond length precisely by holding down the Shift key when dragging an atom. Perhaps we should amend the adroner to give numerical length and angle feedback? |
It was actually a feature request for allowing typing the bond length like we can do with bond angle. |
@deadlyvices I think that adding an adorner with length and angle relative to screen north would be a very valuable addition. |
Or even just displaying the values in the status bar would be incredibly useful |
Yes that would be useful, however
I prefer an adorner as the user's "focus" is on where the mouse cursor is. |
Describe the solution you'd like
Describe alternatives you've considered
I understand that we can drag the bond, we can't do it very precisely.
Edited to put this irrelevant information to the bottom.
In current version, Chem4Word 2020 Beta 8, the default bond length for 1 letter elements (e.g. C,O,N) and 2 letter elements are different (e.g. Ru)
The text was updated successfully, but these errors were encountered: