|
|
|
|
|
|
by gwd
1641 days ago
|
|
|
> I have only been responding to people that are saying that the dot makes this setup "unusable". The machine you're describing is not possible without a dedicated hardware I/O device because the OS always has access to display devices and apps cannot override that. This seems to be the crux of the disagreement in this thread. You're equating the effect of two quite different things: 1. A pop-up that's quite intrusive / potentially embarassing, but has (say) a 1/100 chance of happening any given show, and in any case would only be there for a few seconds; the rest of the show would be unaffected 2. A small but intentionally noticeable orange dot that's there 100% of the show for every show Yes, if you want to be a top level professional, then you can afford to have neither. But I can certainly imagine people / venues where #1 would be considered a normal cost of doing business, but #2 would not. That said, if fixing them both is as easy and inexpensive as people in this thread seem to think, then the small "nudge" by #2 to get them to fix #1 is probably beneficial for the ecosystem overall. |
|
|
You're mis-framing what I'm saying. The effect is the same. There is something on the display that is unwanted. Regardless of what that thing is, the issue at hand is that people do not want things that they didn't choose to be on the display to actually be on the display. It doesn't matter what that is. In this case, it's a small dot but it could have been a little microphone icon or a camera icon or (like Windows) an orange border around the display or literally anything else.
The fact that it didn't affect some people before is great. They were lucky that they didn't have this happen. All I'm saying is that, for years before this change in Monterey, there have been things that pop-up like this on external displays because external displays do not have the ability to prevent the OS from using a display as a display (with a couple exceptions when used with APIs for exclusivity). That's a known problem with using extended displays and it's been known for a while, regardless of the OS you're using. There's also a solution to that problem that's pretty standard in the presentation/production industry.
That being said... there are now multiple solutions for people that both don't break the intention behind this change (they're slightly technical solutions that most people won't do) and allow for app developers themselves to fix the problem (using the APIs already provided to get screen exclusivity).