Hi,
Thanks for the feedback! Please see my comments wrt some of the issues below.
Quote:
|
FIXED - The pointer no longer changes to the resize arrow 10 pixels before the top of the screen. Great!
|
Glad to hear that's fixed.
Quote:
|
STILL NOT WORKING - A 2560x1440 DisplayPort display when rotated 90/180/270 degrees will not recognize 1440x2560. It maxes out at 1080p or 1200x1600.
|
Yes, we're aware of that. There's been no fixes to address that, we had a bug opened with Apple to help us address the scenario. It's still possible this will be fixed before the final release.
Quote:
|
STILL NOT WORKING - Wake from sleep doesn't wake up DisplayLink monitors. They show up in Displays > Arrangement but are black. They can be revived by clicking around in the Displays control panel.
|
We can reproduce something similar. Can you please check if screens reappear without doing anything if you wait 30s-1min after waking the machine up? This would confirm we're seeing the same problem.
Quote:
|
STILL NOT WORKING - Pointer becomes invisible intermittently on non-DisplayLink monitor attached to onboard ATI Radeon video. Happens in Safari and hand cursor is visible on rollover states, but pointer is invisible. Can click on primary monitor or DisplayLink monitor to make pointer visible again.
|
Likely to be OS X or Safari issue. We'll try to reproduce and raise a bug with Apple if confirmed.
Did you see it with any other application?
Quote:
|
STILL NOT WORKING - Safari has lots of flickering on embedded video and HTML5 elements. See www.icloud.com for an example of this. Should be fixed when 10.8.3 is released.
|
That's probably caused by the same change in Safari that caused flickering on "new tab" window as well.
Can you try this workaround to see if it helps: quit Safari, then open Terminal.app and type the following:
Code:
defaults write com.apple.Safari IncludeInternalDebugMenu 1
This enables a hidden Debug menu for Safari. Please go there and choose "Use Buffered Windows", quit Safari, restart it and see if it gets any better. This is just a confirmation for us that the problem is the same, it is by no means a suggested workaround
Many thanks,
Michal