-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Buggy Menubar Behavior on macOS #14917
Comments
Hey @mrclary, thanks for reporting. You need to run Please try that and let us know if it works for you. |
Okay, I'll test that. But these also manifest in the macOS application... |
I cannot get |
Okay, it requires The good news is that only the latter issue manifested in the macOS application, so it would seem that |
For developer instructions... |
Sure, please add a mention to it in our Contributing guide.
This was caused by the migration to the new API and I don't know how to fix it. Maybe there's a way to tell Qt to add that menu entry to the expected place in macOS.
That's because Homebrew Python is built as Mac framework, so it doesn't have that problem (Anaconda's Python is not). |
Will do.
The menu items do find their correct home after activating a dialogue window for the first time...does this suggest that something isn't being set/called/instantiated at application launch? |
Nop, it doesn't ring a bell, sorry. |
Okay, this issue does not seem to manifest on the macOS app artifact from #14950.
All I can think right now is that both are related to different Python versions (or perhaps Qt): Homebrew 3.9.2 on GitHub and Homebrew 3.9.1 local. I will have to investigate further. |
This is misleading. I realized that the artifact for #14950 was built on the 4.x branch. This works for both GitHub (Python 3.9.2) and my local (Python 3.9.1) builds.
This is definitely not the case. The artifact from #14955 (built on the master branch) also exhibits the menu bar issue. So this is definitely something on our end. Furthermore, it manifests under bootstrap with Python 3.7.10, as well as under local installation (launching from conda environment). |
Don't know if it's related, but on bootstrap I see the following in the terminal: |
What issue exactly?
No, that's a bug in Plots and it's unrelated. |
The issue where the menu bar is inactive was resolved by using The issue remains where the menu bar items "Preferences..." and "About Spyder" are located in "Tools" and "Help", respectively, upon launching Spyder (local or GitHub builds, or local bootstrap). After another Spyder window opens (e.g. popup window, or deliberately opening a dialogue window, or ...), then these menu items appear in their proper place in "Spyder" (or "python" if bootstrapping). |
@steff456 @ccordoba12, this issue does not appear to be resolved by #15049, although the behavior has changed somewhat. |
@steff456 I don't know what to make of it either. Were you able to reproduce? |
Yes, I could reproduce it. Sometimes it works faster than others.. But I can reproduce the exact same behavior of your gif |
@mrclary, this could be an issue with Qt 5.9. Could you try with Qt 5.12 from Conda-forge? |
I installed Qt 5.12.9 and it still manifests. conda
build
|
What steps will reproduce the problem?
Upon first launching Spyder (bootstrap), the menubar is disabled. Switching to another application and back to Spyder seems to enable the menubar.
Additionally, some menu items are located incorrectly and have incorrect keyboard shortcuts, such as "Preferences..." and "About Spyder...". After the first activation of these dialogue windows (or any other Spyder window), however, they return to their correct locations with correct keyboard shortcuts.
The text was updated successfully, but these errors were encountered: