Reply from Apple regarding Displaylink bug report

[Carlo]

Originally Posted by christobald

Would be nice to hear more details about this from the Displaylink folks.

How do you know this is Apple's fault? What, specifically, makes you think the problem lies in their software and not yours? And what is Apple's response to that or those reasons?

Hi Christobald and others,

We cannot get into these disputes mainly because the Apple Developer agreements we have signed clearly state that we cannot share any communication between us and Apple (something the first post in this thread is based around).

So this is going to be my last post on this subject I'm afraid.

If you are keen on getting an informed opinion on the subject there are two kind of tests possible without having to write any code:
1) Compare the same use case on 10.8 and 10.9 or later, can be hard for random issues
2) Use a USB or WiFi external screen based on different drivers

(2) Is likely going to be apples vs. oranges up to a point but most OS-related issues are the same.

As any product there are some issues in our court and we are thankful to anyone raising them.
We are also continuing to work on workarounds for the known OS issues and actually hope to be proven wrong about the root cause: it would mean we can do something about them!

As you've seen with the latest 2.3 beta we are actively developing on Mac: you can now connect up to 4 (four!) 4K screens to any Mac that can run 10.8. Who needs a Mac Pro? ;-)

Carlo - Over and out