search

jordanbaird / Ice

Powerful menu bar manager for macOS
https://icemenubar.app
GNU General Public License v3.0
12.81k stars 236 forks source link

App doesn't show all the icons when another app is in focus. #28

Closed maxoliinyk closed 7 months ago

maxoliinyk commented 7 months ago

When editing settings in Ice.app it's gonna be in focus, that means that menubar actions are exclusive to it. In this case, every icon shows as expected.

image

Though, when you use another application, its menubar overlaps icons in Ice.app and some icons are hidden, and there's no way to access them.

image

In my opinion, it's a bug, and should be fixed. For example, Hidden cleans all menubar when you open it.

jordanbaird commented 7 months ago

There's a setting to enable this: "Hide application menus when showing menu bar items". It's at the bottom of the "General" settings pane in 0.6.3.

Also, the next release, 0.7.0, is going to greatly improve this feature by only hiding the application menus when they overlap with the menu bar items.

Edit: Unless you mean that you already have the setting enabled, in which case, I agree that it's a bug and will reopen this issue.

jordanbaird commented 6 months ago

With the changes in 0.7.0, it doesn't hide the application menus every time -- only when the application menu is long enough to prevent menu bar icons from showing. Have you tried it with an app with a long menu to see if it still doesn't work?

maxoliinyk commented 6 months ago

I've already deleted my reply because it started working again. When the issue appeared, the menu bar was long enough to hide some of my icons.

I found out that this issue doesn't work as intended when we have "Currently Sharing" icon

3884

And works great without it. Should I fill a separate bug report?

36425
jordanbaird commented 6 months ago

Interesting. Yes, if you could open a separate issue for this, that would be great.

Edit: Actually, after some quick investigating, it looks like it was being caused by some experimental code that accidentally made it into the 0.7.0 release. I've already reverted it, so I think it should already be fixed. If the problem persists once the next release is out, then I would say open the new issue.