-
-
Notifications
You must be signed in to change notification settings - Fork 181
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
Selecting atoms with Dipole Moment turned on causes crash #1806
Comments
I can try to put back the delay timer to minimize repeating calls to re-compute the dipole. It's currently called anytime it's re-rendering. I'm not sure why it's not being re-calculated with the manipulation tool. I'd also want to understand why there's a crash if you can run the debugging. |
I'm getting all kinds of weird crashes now. I pushed #1809 until I have time to figure out what's happening... |
Here are the build results |
Here are the build results |
Here are the build results |
Avogadro version: (please complete the following information from the About box):
beta
branch and compiled from sourceDesktop version: (please complete the following information):
Describe the bug
If the Dipole Moment display type is checked, click-and-drag with the Selection Tool results in a crash.
The accompanying terminal output is:
Note that the OBProcess line is printed many times (86 times in this case).
Selecting and deselecting individual atoms is ok, even when multiple are selected by repeated Ctrl+Click. Each individual click is accompanied by a printed
OBProcess::executeObabel: Running "/prefix/bin/obabel" "-icml -onul --partialcharge mmff94 --print"
.Presumably the dipole moment is being recalculated with every mouse action, even though using the Selection Tool in the view pane never results in a change in the dipole.
As an aside, the dipole is in contrast not currently being recalculated when the Manipulation Tool is used.
The text was updated successfully, but these errors were encountered: