2.5 beta 2

[dave_w]

Originally Posted by Carlo

Hi Dave,

Could you describe the kind of issues are you experiencing on Yosemite?

Carlo

Sure. Every time I put the screen to sleep using a hot corner or by inactivity, the DisplayLink-connected screen would not wake up. The other displays (both the inbuilt and DisplayPort screen) would both awake. From memory disconnecting and reconnecting or restarting rectified the issue but obviously wasn't practical.

At other times I also had some inconsistent issues where nothing would show except the cursor and a black background on the DisplayLink monitor. Minimising windows via the menu bar would show the minimising animation to the dock on the DisplayPort screen from where they should have been on the DisplayLink monitor.

While I'm at it (not sure if it's been resolved already) but I had to start using the DisplayPort/Thunderbolt port rather than the second output of the Kensington dock a while back due to inconsistent arrangement of the monitors every time I connected. This happened after moving to Yosemite, and not before.

Dave

[Carlo]

Originally Posted by dave_w

Sure. Every time I put the screen to sleep using a hot corner or by inactivity, the DisplayLink-connected screen would not wake up. The other displays (both the inbuilt and DisplayPort screen) would both awake. From memory disconnecting and reconnecting or restarting rectified the issue but obviously wasn't practical.

At other times I also had some inconsistent issues where nothing would show except the cursor and a black background on the DisplayLink monitor. Minimising windows via the menu bar would show the minimising animation to the dock on the DisplayPort screen from where they should have been on the DisplayLink monitor.

While I'm at it (not sure if it's been resolved already) but I had to start using the DisplayPort/Thunderbolt port rather than the second output of the Kensington dock a while back due to inconsistent arrangement of the monitors every time I connected. This happened after moving to Yosemite, and not before.

Dave

Thank you Dave,

We'll try to reproduce the first issue, the second is already being investigated. We introduced a workaround for the third issue in version 2.4, that should be fine now.

Best regards,
Carlo