Hi Marcus, I wanted to follow-up about an off-list discussion with Avogadro v2. Between v0.7, and the current git master (0.8?) there's now a clear UI division between "edit" and "view" molecules.
Can you outline some of the real reasons for this behind the scenes, particularly on the UI side? I think this is currently a usability nightmare and I'd like to make sure we can work past this or write up conversion code that allows tools, extensions, etc. to convert back and forth. My big use-case concern is the Auto Optimize tool, which I'm trying to design for Avogadro v2's very different architecture. For example, let's say a user wants to set a measurement between two atoms (view). Then they switch to the Auto Optimize tool (edit) and start pushing atoms around. In Avogadro v1, this wasn't a problem. The measurements would update while the optimization occurred in a different thread. How can this work in Avogadro v2? Thanks, -Geoff ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ Avogadro-devel mailing list Avogadro-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/avogadro-devel
