additionally:
Probably this bug caused by differences in decimal separator in locales. Russian locale uses "," as separator. When I open any file in Avogadro now, all coordinates becomes integer values (in coordinate editor or after saving).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What version of OpenBabel are you using? There were locale issues in OpenBabel when loading files with locales that used the comma separator, but that was fixed quite some time ago.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Please try to change your Qt theme to something else, e.g. Oxygen. Also, specify your Linux distribution (I guess you are under Linux, aren't you?)
Currently Qt theme is GTK. Theme changing doesn't affect behavior.
Linux distribution is Gentoo. version Qt -4.6.3
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Old Bugs"
Confirm this.
Ubuntu 10.10 Qt 4.7.0 Avogadro 1.0.1 from Ubuntu repos.
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Old Bugs"
additionally:
Probably this bug caused by differences in decimal separator in locales. Russian locale uses "," as separator. When I open any file in Avogadro now, all coordinates becomes integer values (in coordinate editor or after saving).
What version of OpenBabel are you using? There were locale issues in OpenBabel when loading files with locales that used the comma separator, but that was fixed quite some time ago.
If we do not receive further information from the poster, I'm closing this bug as "Works for Me."
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).