Now that the flying edges works for orbitals (thanks @perminder-17) I’ll be adding in the orbital table feature this week (e.g., see the list of orbitals and click to render)
A few fixups in the spectra window, including UV/Vis and CD spectra for my students
At least an attempt at packaging the Qt6 builds for Mac and Windows
Sounds good to me the way you’ve laid it out, honestly If you manage to get all that in then this release will have a pretty full feature set – you’ve added a lot this year.
Having almost all the features you plan in place for 1.100 hopefully then allow the focus to be polish and bug fixes running up to 2.0. It’s a release candidate, in a way, after the long series of betas.
And a bunch of bug reports from non-nightly users migrating to the new release will help with ironing out the remaining creases I’m sure
I’m referring to your bug report - that a submenu sometimes shows up on hover. That’s not a visual bug?
I can’t reproduce it though.
Can you upload a screenshot of this submenu?
What locale are you using?
Some of the weird menu issues have turned out to be locale-related
Oh… I don’t think the Windows issue is affecting “half of Windows installs.” Clearly a significant number of Windows users, but I’ve gone around to a bunch of folks at Pitt (and tried on my son’s desktop) and it’s clearly some subset of Windows 10 users. Important to fix, certainly. But I don’t know about “half of Windows installs.”
Other way round. The submenu that normally shows, fails to show on hover. Simply nothing happens. So it might be visual (it “shows” but is invisible) but I think it’s more likely a logic bug.
No it seems to be an openSUSE issue, and the Flatpak is immune, which is what makes me think it’s about some dependency, but no idea what.
I also have a vague hope it’s connected to the same plugin JSON issue as the bug with the downloader and will be fixed now, but I am flying shortly and won’t have chance to check
Sadly not going to have time. Screenshot wouldn’t tell you much, it looks literally the same as if the plugin’s menu entry was a normal single command and not a submenu. Locale might be relevant, as sometimes I change it to US English from system to check things. I don’t know if you’ll be able to reproduce it by switching the language?
Ok, that’s reassuring. Was worried it was borked for all Windows 10 users!
Just to bump this up … it’s now the end of 2024 and still a few to squash. I’d ideally like to make sure the “can’t launch for some users on Windows 10” is fixed. And I think @brockdyer03 is seeing some crashing in the new MO window.
I’m traveling the rest of this week, so we’ll fix things up in January. (And then more releases as needed.)
As to the Windows issue, at the very least, one user indicated on BlueSky that it’s now working on Windows:
Since it’s been hard to track down users for testing, I think I’m going to be pragmatic and release - if 1.100 still has the same problem, we’ll get more bug reports
I recently found my old laptop with Windows 11 on it. Since no one is using that for now, I have a playground where I can test stuff so that I don’t mess up my main desktop. I was just using it to double/triple check that Python is no longer required for force fields (it definitely is not required), and if need be I can probably go for a full factory reset on it to test stuff.
I was also able to find a Windows 10 computer that I can use briefly, and it seems that Av2 isn’t working. It is running version 10.0.19045 of Windows 10 Pro, and I was using the nightly build off two.avogadro.cc.
Edit: I read that bluesky thread you linked, and I think it’s a Windows update that fixed that user’s problem. I know for a fact it works fine on Windows 11, so it must be a problem with an older version of Win 10 that causes the issue.
Yes, that seems likely. I had hoped it was related to some changes in OpenGL. But if you can send me the avogadro2.log from one of those nightly builds, it will have a bunch more debugging information (e.g., it prints every feature as it loads).
Too bad that the nightly build doesn’t work though. I was hoping we’d fixed it already.
Turns out the version of windows that I was running was the most up-to-date version and build. After some debugging attempts, it may be an issue with a graphics driver, but I am unsure.
)
Features
Bugs
Here’s to a great 2025!