![]() The bugs are almost always closed as duplicate of another bug, which, of course, you can't see because the bug tracker is private. Sometimes this happens even if they asked you to try the beta version! When you try to reproduce the bug on multiple versions, they close your bug if you reproduced it on beta versions, because beta versions are unsupported, even though the bug affects release versions. They take forever to answer, and ask for things that you have already provided in your original issue. I can’t recall whether Activity Monitor has any historical/time-series views built in? If it does, then if you hide Activity Monitor with those active, it should keep using CPU, to gather the data for that view, whether it’s rendering it or not. This might be down to Activity Monitor being written to respond to a message letting it know that its view is entirely obscured, and the Activity Monitor main-window view-controller deciding in response that there’s no point in it polling the system if all it’s going to do when re-visible is discard all the stuff it learned in the mean time and re-poll again to get the newest data for the view. > It does for me, which is why I keep it hidden when I’m not actively using it. (They might have a lower update rate, though.) I believe it’s just using the same call into the compositor that Mission Control uses to display your windows and spaces. ![]() ![]() Nah, it updates (.as far as I can recall.) Try opening a chat client, minimizing the chat window, and then sending a message from another device to yourself. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |