-
All replies
-
Helpful answers
-
Sep 22, 2016 9:55 AM in response to simimaby JimmyCMPIT,★Helpfulin the display control panel click on the Scaled while holding down the OPTION key
-
Sep 25, 2016 2:55 AM in response to simimaby simima,Well, I thought it to be solved - but it isn't. HiDPI remains an issue...
I have posted another thread with more details in the Mac OS Sierra forum.
-
Sep 25, 2016 5:24 AM in response to simimaby BobHarris,Please file a Bug report so that Apple is aware _AND_ that customers care and want support for external monitors besides 1080p
BugReporter (Free ADC (Apple Developer Connection) account needed for BugReporter)
<http://bugreporter.apple.com>
Anyone can get a free ADC account at:
-
Sep 25, 2016 7:21 AM in response to BobHarrisby simima,Thanks Bob
I did exactly that. Lets see what happens.
Maybe Sierra has significant changes under the hood, but what concerns robustness, I'm quite disappointed by that initial Sierra release... I haven't had to use so many force shutdowns and didn't experience such erratic behaviour in a while.
Lets hope Apple will fix it.
-
Sep 28, 2016 12:05 PM in response to simimaby postenterprise,This isn't solved. But here is my workaround.
- Turn on macbook and keep it open. Monitor is also on and plugged in via displayport.
- Login.
- When desktops appear on both macbook and monitor, shut lid to clamshell mode.
- Monitor will have wrong resolution and options will not include scales hidpi modes that I used under el capitan.
- Restart from top left menu.
- Now log in and your will have previous resolutions and modes available.
I use my macbook 13" early 2015 in clamshell mode with a 4k NEC EA244UHD professional monitor . as well as mobile on the move.
I really am disappointed by Apple's policy of denial and silence on critical issues. Remember the wi-fi issue that took months to fix... On devices with no Ethernet!
Apple has nothing to lose and lots to gain by following the open transparent bug tracking followed by much open source (which Apple incorporates into macosx).
-
Sep 28, 2016 12:13 PM in response to postenterpriseby simima,Right, it isn't solved. I just can't edit my post anymore... it is in the wrong forum anyway, but when I had posted it, the Mac OS Sierra forum wasn't even available...!
I know your workaround, I do sort of the same. Takes me 5-10 restarts a day to keep thinks workable. Please file a bug report bugreport.apple.com, so Apple knows about... I doubt they read the forums, which I find a pity.
Let's hope Apple will fix this soon. Apple and displays, what a drama.
-
Sep 28, 2016 12:22 PM in response to simimaby postenterprise,I have filed a bug report.
In fact I registered for the first time to do that. (And post here)
I didn't get any follow up.
Seriously - for a premium company offering a "pro" system ... the testing is worse than many £50k startups .. I wish I was joking.
-
Sep 28, 2016 4:47 PM in response to postenterpriseby BobHarris,Apple has nothing to lose and lots to gain by following the open transparent bug tracking followed by much open source (which Apple incorporates into macosx).
Commercial companies that promise something, create expectations that if not provided, result in problems (including problems that include lawyers).
The developers that deal with bugs are not in a position to make any promises, because they cannot predict what will and what will not make it into a bug fix update, or a next release upgrade. Often times they do not know at the start of a bug if it will be a simple fix, or if the code requires a major rewrite, or worse the entire infrastructure needs to be redone.
Speaking as someone that has been involved in the development of commercial Unix operating systems (other fortune 100 computer companies, never for Apple), developers are never allowed to say when something will be fixed. And when they mistakenly do say when something will happen, management tends to "Have a Talk" with said developer. After that, said developer stops mentioning when something will be fixed, or giving too many details in a bug report. And some bug reporting systems do not publish internal developer comments that can only be seen by other developers.
Open Source is totally different. If someone says it will be done by X, and then does not deliver, they often times do not have a manager to walk into their office and have that "Talk". Then again maybe Redhat works differently (or other large companies contributing to Open Source), but I would bet that their managers would discourage them from saying too much in a bug report.
-
Sep 29, 2016 12:54 AM in response to BobHarrisby postenterprise,Thanks for an considered reply.
The key here is is that openness and transprency is incredible helpful, .... But isn't the same as making unrealistic or unwarranted promises.
Many many serious and successful companies do understand that.