![]() |
|
|
|
|
#1 |
|
Junior Member
Join Date: Mar 2013
Posts: 4
|
When i install the latest driver into my 17"mbp running 10.8.3 it causes issues where i cant click-drag-and-drop anything. It is as if my left mouse button is not released and the item i drag stays selected and linked to the mouse movement. When I uninstall the driver this goes away. This makes it impossible to work.
I am running 10.8.3 on a 2010 MBP (2.8GHz Core 2 duo, 8GB Ram), with the MonoPrice USB 2.0 to VGA display adapter and the 2.0 Beta 1 Driver. Usb Mouse. Anyone experience this? I have been unable to search and find this specifically. |
|
|
|
|
|
#2 |
|
Junior Member
Join Date: Mar 2013
Posts: 4
|
Can anyone say they have the same issue?
|
|
|
|
|
|
#3 |
|
Junior Member
Join Date: Mar 2013
Posts: 4
|
Quite Annoying.
|
|
|
|
|
|
#4 |
|
Senior Member
Join Date: Feb 2009
Posts: 1,561
|
I think this is a known issue and is a bug in the Apple OS. Does the problem get fixed if you sleep and then wake the computer?
Thanks Wim |
|
|
|
|
|
#5 |
|
Junior Member
Join Date: Mar 2013
Posts: 4
|
Interesting,
It does go away with sleep/wake. The new 2.0 software didn't fix it either. AT least this does, which at least allows me to work. Thanks. |
|
|
|
|
|
#6 |
|
Mac Team
Join Date: Feb 2009
Posts: 606
|
We have an automated workaround for this OS issue in the 2.0 driver. To make sure it can run, "Require password for sleep and screen saver" option must be either disabled or enabled but set to a value different than "immediately".
"After 5 seconds" or higher is ok. The option can be set in System prefs->Security&Privacy. Cheers, Carlo |
|
|
|
|
|
#7 |
|
Junior Member
Join Date: May 2013
Posts: 1
|
Hi there,
Like many of you, I got the dreaded drag-and-drop issue after installing the displaylink drivers on my MBP 2008 (version 2.0). Totally messed up my workflow ![]() ![]() so I uninstalled it (thanks for the uninstaller guys!!) and everything worked fine again. However, this meant no extra display.The funny thing is however that I did not get the same problems on my MB 2008 Unibody so I got the idea that maybe, just maybe, something went wrong during the installation on the MBP. To test this, I re-installed the 2.0 drivers on the MBP and, to my welcome suprise, all seems to work fine. I rebooted and done several shutdown-boot-ups to see whether the problem re-appears. So far, no problems. I don't know of this all makes any sense and to be honest, I don't really care as long as works again. Hope this helps also with others! Good luck! |
|
|
|
![]() |
|
|