5 ms·

Free upgrades can still come at a cost. Multi-monitor full-screen was broken from 10.7 through 10.8. Thousands complained, Apple claimed it a feature. Not fix

Free upgrades can still come at a cost. Multi-monitor full-screen was broken from 10.7 through 10.8. Thousands complained, Apple claimed it a feature. Not fixable, not tweakable, not reversible. 10.6 or one full-screen monitor at a time. Fuck off, Apple.

kordless 12y ago
> Fuck off, Apple. Log off, user.
- deleted 12y ago
  [deleted]
- deleted 12y ago
  [deleted]
- deleted 12y ago
  [deleted]
- deleted 12y ago
  [deleted]
- yourad_io 12y ago
  I took it personally because my vendor condescendingly told me that the fact that I can't use my environment (multi-monitor) the way I wanted (full-screening applications) was actually a feature. Apple was telling me to STFU or GTFO. So I did the latter :)
  - kordless 12y ago
    All you can do is seek your own joy. Expecting others to do that for you is setting expectations. Not sure why I got the downvotes, but I'm happy you got free of OSX. I'm still hanging in there...for now.
ridiculous_fish 12y ago
I worked on the full screen feature in 10.7 through 10.9! Full screen in 10.7 and 10.8 did render secondary displays useless. But it was a new feature in 10.7, so there was nothing to reverse. You can't take Safari, Mail, etc. full screen in 10.6. Perhaps there was an app you used that switched from a custom full screen implementation to the system one, and so regressed on secondary displays?
- yourad_io 12y ago
  VLC, iTerm (& Terminal? I think), Chrome, Firefox, ... Most things I used had some sort of full-screen mode that was then "hijacked" by 10.7's native full-screen mode. I say "hijacked" because even versions that were pre-Lion would somehow end up using the native "feature". The thing to reverse would have been the "switch to new workspace when full-screening" - or at the very least make it optional. Certainly not respond "that's a feature" and close as "working as expected" when thousands complain. I failed to see the value in that feature even with a single screen. An action that used to happen instantaneously now took 1-2s. and a dizzying sliding animation. (Many a flow was lost to toggling full-screen by accident - whereas previously you could toggle/toggle back immediately without losing your mental state - surely you appreciate that as a developer?).
  - ridiculous_fish 12y ago
    Ok, I get it: you don't like how the system full screen integrates with workspaces, and you were peeved when other apps adopted it in place of their own implementations. Of course Apple did not "hijack" anything: full screen support has always been strictly opt-in. But apps would feel pressure to adopt the system implementation. Full screen was an effort to make OS X more usable on small displays - recall that the 11" MacBook Air had just shipped. It didn't make much sense for media playback apps to adopt the system full screen mode, especially as it was in 10.7-8. I would have loved to enable a system mode where full screen windows could coexist in the same workspace as unrelated windows, but this would have been a new feature, not something we could have achieved by reversing anything. And eventually Apple did enable a new mode, which was what shipped in 10.9. Oh, and if you filed a bug, then whoever closed it as "working as expected" made a mistake. There was a (heavily duped) bug tracking the uselessness of secondary displays in FS, and it was closed when 10.9 shipped. I may even have been the one to close it, I don't remember.
threeseed 12y ago
How was it broken ? It worked exactly the same as before only Apple added full screen mode which didnt work in an ideal way. But guess what you don't have to use it. Just maximise your windows normally or use one of the many free tools to do it via keystrokes. But yeh fuck Apple for offering free OS upgrades that are completely optional.

kordless 12y ago

> Fuck off, Apple. Log off, user.

deleted 12y ago
[deleted]
deleted 12y ago
[deleted]
deleted 12y ago
[deleted]
deleted 12y ago
[deleted]
yourad_io 12y ago
I took it personally because my vendor condescendingly told me that the fact that I can't use my environment (multi-monitor) the way I wanted (full-screening applications) was actually a feature. Apple was telling me to STFU or GTFO. So I did the latter :)
- kordless 12y ago
  All you can do is seek your own joy. Expecting others to do that for you is setting expectations. Not sure why I got the downvotes, but I'm happy you got free of OSX. I'm still hanging in there...for now.

ridiculous_fish 12y ago

I worked on the full screen feature in 10.7 through 10.9! Full screen in 10.7 and 10.8 did render secondary displays useless. But it was a new feature in 10.7, so there was nothing to reverse. You can't take Safari, Mail, etc. full screen in 10.6. Perhaps there was an app you used that switched from a custom full screen implementation to the system one, and so regressed on secondary displays?

yourad_io 12y ago
VLC, iTerm (& Terminal? I think), Chrome, Firefox, ... Most things I used had some sort of full-screen mode that was then "hijacked" by 10.7's native full-screen mode. I say "hijacked" because even versions that were pre-Lion would somehow end up using the native "feature". The thing to reverse would have been the "switch to new workspace when full-screening" - or at the very least make it optional. Certainly not respond "that's a feature" and close as "working as expected" when thousands complain. I failed to see the value in that feature even with a single screen. An action that used to happen instantaneously now took 1-2s. and a dizzying sliding animation. (Many a flow was lost to toggling full-screen by accident - whereas previously you could toggle/toggle back immediately without losing your mental state - surely you appreciate that as a developer?).
- ridiculous_fish 12y ago
  Ok, I get it: you don't like how the system full screen integrates with workspaces, and you were peeved when other apps adopted it in place of their own implementations. Of course Apple did not "hijack" anything: full screen support has always been strictly opt-in. But apps would feel pressure to adopt the system implementation. Full screen was an effort to make OS X more usable on small displays - recall that the 11" MacBook Air had just shipped. It didn't make much sense for media playback apps to adopt the system full screen mode, especially as it was in 10.7-8. I would have loved to enable a system mode where full screen windows could coexist in the same workspace as unrelated windows, but this would have been a new feature, not something we could have achieved by reversing anything. And eventually Apple did enable a new mode, which was what shipped in 10.9. Oh, and if you filed a bug, then whoever closed it as "working as expected" made a mistake. There was a (heavily duped) bug tracking the uselessness of secondary displays in FS, and it was closed when 10.9 shipped. I may even have been the one to close it, I don't remember.

threeseed 12y ago

How was it broken ? It worked exactly the same as before only Apple added full screen mode which didnt work in an ideal way. But guess what you don't have to use it. Just maximise your windows normally or use one of the many free tools to do it via keystrokes. But yeh fuck Apple for offering free OS upgrades that are completely optional.