Hi!
I've created one more variant too.
Here are the source (Affinity Designer) and icns files: https://github.com/plashenkov/Big-Sur-icons
Symbols are taken from @giovannimariacusaro variant (I'll note about it in a readme).
Here is how it looks like: https://take.ms/wAUzS
It doesn't try to mimic Terminal app icon though.
Feel free to use it if you like it.
Hi!
Sometimes titlebar color doesn't match tabs color. For example, let's use the light theme. In case iTerm window is active everything is OK. When window is inactive (for example, a window of another app is active, or you clicked a desktop, so iTerm app is fully inactive), everything is OK as well — window titlebar becomes white, tabs also become ~white. Everything is like everywhere in macOS. Now open iTerm preferences, or iTerm "about" window, or profiles... tabs become white (as they should), but titlebar remains grey, as it is still active.
If I understand correctly, the titlebar as well as tabs are not macOS native, but emulated?
Detailed steps to reproduce the problem:
What should have happened: titlebar and tabs state should be consistent. When another iTerm window is opened, titlebar should be in "inactive" state (this is a native behaviour in macOS).
Thank you!
Yep. Thanks!
Ah, I see, not all macOS apps act this way. For example, default macOS Preview app: main window looks still "active" when "about" window or "preferences" window opened.
Hi!
Sometimes titlebar color doesn't match tabs color. For example, let's use the light theme. In case iTerm window is active everything is OK. When window is inactive (for example, a window of another app is active, or you clicked a desktop, so iTerm app is fully inactive), everything is OK as well — window titlebar becomes white, tabs also become ~white. Everything is like everywhere in macOS. Now open iTerm preferences, or iTerm "about" window, or profiles... tabs become white (as they should), but titlebar remains grey, as it is still active.
If I understand correctly, the titlebar as well as tabs are not macOS native, but emulated?
Detailed steps to reproduce the problem:
What should have happened: titlebar and tabs state should be consistent. When another iTerm window is opened, titlebar should be in "inactive" state (this is a native behaviour in macOS).
Thank you!
Hey George,
I've just downloaded a nightly build which includes this fix. I can see that tabs and titlebar act synchronously now. But what I noticed: when you open preferences window, about window, etc., the main window is still looks like it is active. It is grey, not white. Default macOS behaviour is to "deactivate" a window. For example, look at Finder. Open Finder -> Preferences, you will notice that Finder window is now "white". When you do the same for iTerm, it stays grey. Or is this intentionally, maybe?
That's great! Thank you :)
Hi!
Sometimes titlebar color doesn't match tabs color. For example, let's use the light theme. In case iTerm window is active everything is OK. When window is inactive (for example, a window of another app is active, or you clicked a desktop, so iTerm app is fully inactive), everything is OK as well — window titlebar becomes white, tabs also become ~white. Everything is like everywhere in macOS. Now open iTerm preferences, or iTerm "about" window, or profiles... tabs become white (as they should), but titlebar remains grey, as it is still active.
If I understand correctly, the titlebar as well as tabs are not macOS native, but emulated?
Detailed steps to reproduce the problem:
What should have happened: titlebar and tabs state should be consistent. When another iTerm window is opened, titlebar should be in "inactive" state (this is a native behaviour in macOS).
Thank you!
Nope; it still happens: http://take.ms/msrn5
(I've renamed my .bash_profile
to .bash_profile.BAK
; it looks like I do not have .bashrc
and .profile
at all).
What can be unusual? My .bash_profile
contains:
source "/path/to/powerline.sh"
(https://github.com/plashenkov/powerline/blob/master/powerline.sh)
I do not know could it cause such type of error. I'll try to remove it and I'll post the result here.
Hi, George.
Here is a screencast: http://take.ms/IFQZs (the crash is at the end).
What I do: I simply close tab (sometimes app exits, sometimes remains opened), then start app again. If I do this the problem pops up relatively often.
Sometimes "broken" tab is single, sometimes there are 2 such tabs.
Other screenshots with Console.app:
http://take.ms/HyoU6
http://take.ms/rc2xt