6 ms·

Let's say you're giving a PowerPoint and an app crashes in the background (for whatever reason). PowerPoint cannot prevent an OS alert from popping up on the sc

Let's say you're giving a PowerPoint and an app crashes in the background (for whatever reason). PowerPoint cannot prevent an OS alert from popping up on the screen. macOS has functions to hide the menu bar in full-screen apps but it does not have functions to stop other OS chrome from appearing.

_ph_ 5y ago
Yes, there are circumstances where the OS is overriding the full screen mode of an application. Usually only in the case of very significant events or user interaction - like moving your mouse to the screen top will show the menu bar on Mac OS. But all of this isn't shown permanentely on top of the full screen app and only triggered by special events.
- dkonofalski 5y ago
  That's not the point. The point is that it can happen during a performance unless you're using a dedicated piece of I/O hardware. They give you 100% control over what gets outputted. Just because people were ok with what the OS displayed before doesn't mean that that it couldn't.
  - _ph_ 5y ago
    We are talking about different things. Yes, you cannot 100% prevent a dialog to appear without custom hardware. And of course, even with custom hardware, the OS could decide to disable it to stop output to it. But this isn't the point. So far, there were full screen modes and the OS would honor those under regular circumstances. When I run a Linux VM on a Mac, I can see the whole Linux desktop full screen. I don't want MacOS draw colored dots on top of my Linux VM. People probably don't want yellow dots on their PowerPoint presentation.
    - dkonofalski 5y ago
      No, we're not. The only difference in what we're talking about is that you were ok with the exact same thing as now because you liked/agreed with what the OS was putting on the screen. Whether it was because it was rare or uncommon is completely besides the point. This whole thread is about people who are saying that the dot makes the display "unusable". If that was the case, then any other OS chrome would also make it unusable.
      - _ph_ 5y ago
        No, that is wrong. So far the OS didn't display anything permanentely on top of a full screen app. It was only as a reaction to user input and exceptional situations. Especially (under MacOS), when the full screen app was runninning on a secondary screen. I can only hope/assume, I misunderstood the article or this is just a bug.
        dkonofalski 5y ago
        No, it's not wrong. That's what I said. It still doesn't do anything permanently. It only does it if you're using audio input actively. That's a reaction to user input. You're enabling a recording device and that's what triggers this OS chrome. Whether you agree with that is irrelevant since full-screen mode has always allowed OS chrome.
        _ph_ 5y ago
        That is something entirely different. When I said active user input, it was a concrete reaction to a specific user action, like moving the mouse at the menu area. There is no such user action, which would be triggering a sound recording. This is about running applications in the background. According to the article, that would taint the full screen mode constantly and not transiently as the other actions. It is fully sufficently, if that happens on the primary screen.
        dkonofalski 5y ago
        Then you didn't understand the article. The dot is only on-screen when an audio recording device is active.
yjftsjthsd-h 5y ago
Isn't that Do Not Disturb mode?

_ph_ 5y ago

Yes, there are circumstances where the OS is overriding the full screen mode of an application. Usually only in the case of very significant events or user interaction - like moving your mouse to the screen top will show the menu bar on Mac OS. But all of this isn't shown permanentely on top of the full screen app and only triggered by special events.

dkonofalski 5y ago
That's not the point. The point is that it can happen during a performance unless you're using a dedicated piece of I/O hardware. They give you 100% control over what gets outputted. Just because people were ok with what the OS displayed before doesn't mean that that it couldn't.
- _ph_ 5y ago
  We are talking about different things. Yes, you cannot 100% prevent a dialog to appear without custom hardware. And of course, even with custom hardware, the OS could decide to disable it to stop output to it. But this isn't the point. So far, there were full screen modes and the OS would honor those under regular circumstances. When I run a Linux VM on a Mac, I can see the whole Linux desktop full screen. I don't want MacOS draw colored dots on top of my Linux VM. People probably don't want yellow dots on their PowerPoint presentation.
  - dkonofalski 5y ago
    No, we're not. The only difference in what we're talking about is that you were ok with the exact same thing as now because you liked/agreed with what the OS was putting on the screen. Whether it was because it was rare or uncommon is completely besides the point. This whole thread is about people who are saying that the dot makes the display "unusable". If that was the case, then any other OS chrome would also make it unusable.
    - _ph_ 5y ago
      No, that is wrong. So far the OS didn't display anything permanentely on top of a full screen app. It was only as a reaction to user input and exceptional situations. Especially (under MacOS), when the full screen app was runninning on a secondary screen. I can only hope/assume, I misunderstood the article or this is just a bug.
      - dkonofalski 5y ago
        No, it's not wrong. That's what I said. It still doesn't do anything permanently. It only does it if you're using audio input actively. That's a reaction to user input. You're enabling a recording device and that's what triggers this OS chrome. Whether you agree with that is irrelevant since full-screen mode has always allowed OS chrome.
        _ph_ 5y ago
        That is something entirely different. When I said active user input, it was a concrete reaction to a specific user action, like moving the mouse at the menu area. There is no such user action, which would be triggering a sound recording. This is about running applications in the background. According to the article, that would taint the full screen mode constantly and not transiently as the other actions. It is fully sufficently, if that happens on the primary screen.
        dkonofalski 5y ago
        Then you didn't understand the article. The dot is only on-screen when an audio recording device is active.

yjftsjthsd-h 5y ago

Isn't that Do Not Disturb mode?