4 ms·
why else would these blatant multi-monitor issues exist if not to intentionally hurt me? I'm using Lion with multiple monitors, too, and have been annoyed by t
by johnthedebs 15y ago
why else would these blatant multi-monitor issues exist if not to intentionally hurt me?
I'm using Lion with multiple monitors, too, and have been annoyed by this. But the company that sells https://www.apple.com/displays/ https://www.apple.com/displays/ definitely didn't do this to intentionally hurt users with multiple monitors.
My assumption is that, because of the dramatic changes to the desktop workflow in Lion, they needed to cut some features to meet summer deadline. Since relatively few users need multiple monitors, that's one area where they skimped.
We'll probably see some sanity restored in a minor update to the OS.
- tseabrooks 15y agoHah! I don't actually believe it was to "hurt" anyone, It was just a bit of hyperbole. I do, however, think that Apple's vision for the future of desktop computing is sans multiple monitors.
- llambda 15y ago> I do, however, think that Apple's vision for the future of desktop computing is sans multiple monitors. Because they fudged support in the initial release of Lion? Get real. If you're so effected by it, downgrade until there's an update that fixes it. But don't assume that the workstation of choice among graphic artists is going to completely drop multi-monitor support just because it isn't exactly how you want it right at release.
- orangecat 15y agoApple will take money from pro users but doesn't care about them at all from a strategic perspective. See Final Cut Pro X and the total lack of consideration for businesses running the previous version. No, Mac OS X won't suddenly drop support for multiple monitors, but I don't expect Apple to devote much time to making new features work well with them.
- masklinn 15y ago> I do, however, think that Apple's vision for the future of desktop computing is sans multiple monitors. Which is very weird considering their Thunderbolt monitor is specifically marketed for use with their laptops, and for chainability (so not just 2 monitors but at least 3).
- johnthedebs 15y agoYup. This image (from Apple's marketing material) makes me optimistic: https://ssl.apple.com/displays/images/overview_hero2.jpg https://ssl.apple.com/displays/images/overview_hero2.jpg
- tolmasky 15y agoI think some of the issues border on intentional. A particularly infuriating example is how DVD Player really did go BACKWARDS. There used to be an option in DVD Player's preferences for whether to black out the other screen when in fullscreen or to leave it usable. DVD Player was perfect before (I used to watch a movie on one monitor and code on the other). They actually went in and removed this. DVD Player now has the "new" behavior of 1) forcing me to full screen on the right hand screen regardless of where the DVD window was originally, and 2) Putting felt all over the other screen. Its incredibly annoying even when I DONT want to use the other screen, because I certainly don't want distracting full brightness felt on the other screen. I simply cannot understand this choice. Who went in and DELETED those lines of code? I don't think we'll see any sanity return to this BTW. The very foundation of Full Screen is made in such a way to make it conceptually difficult to fix. All these problems stem from the decision that full screen should ALSO throw you into another new space, which makes it incompatible with the old workflows of having other apps running on the other screen. It was such a silly decision (to support "swiping" I guess?) Full screen already existed before, all they should have done is update the iLife/iWork apps to support the old full screen and encouraged developers to do the same. Instead they over engineered this complex system of spaces (a feature that only PRO users are used to BTW) and broke old features. I really don't understand it.
- adamjernst 15y agoI doubt it was intentional. DVD Player went from using their own custom full-screen code to the new system standard full-screen mode (as evidenced by the full-screen button in the title bar). This probably let them delete hundreds of lines of code; it also causes the problems you mentioned. Be patient; I'm sure they'll fix it soon.