![]() |
Problems with Microsoft Publisher
I have a curious problem with the use of MS Publisher 2016 on my add. screens powered with DisplayLink
My config:
Publisher is working without issues on the internal screen. On the additional screens powered with displaylink I have the curious issue that the mouse jumps to the left out of the publisher window, when I am trying to manipulate a grapical element (moveing or resizing it) The mouse moves the element to the border of the publisher window. Trying to move back the element to the origin place is like the mouse is jumpiung again and again to the left... I have two screens on the docking, it happens on both screens. I have not found other issues escept some freezings, but this I cannot reproduce. I have no idea how I can resolve it... Many thanks in advance for your support Harmen |
Hello Harmen,
Thank you for the detailed description. Would you please be able to try to reproduce with 8.0 M3? We have introduced a new feature in 8.1 M0 around the mouse cursor, and I would like to see if it is related or if it was present before we did that work. Kind regards, Alban |
2 Attachment(s)
Hello Alban,
thanks for your answer and sorry for my late reply... I have downgraded the driver to Version 8.0.903.0. no change. The issues ist still the same. Inaddition to the named issues I have recognized a function I cannot resolve either, and I think this is based on the same problem. When I am clicking in a field to enter a username or Password, chrome supports me by clicking in the field with a list of possible user and passwords. This list is normally under and in a direct contact to the field. It is correct on my internal screen. On the screen powered with displaylink last driver or current, the list is up to 10 cm away from the field, somewhere on the right... I have attached 2 screenshots to show this... Cheers Harmen |
Hello Harmen,
We do not have access to the cursor position on 8.0 for that version of Windows. This is a feature we added in 8.1 to take over from the OS and make it smoother. Therefore, we would not be able to move it or influence its movement from our driver. If this behaviour is specific to Publisher, I would recommend contacting your Microsoft contact. The native DisplayLink support on that version of Windows was co-developed with Microsoft so they have experts in that domain... I mean they wrote both Publisher and the OS as well. Similarly, we do not have access to objects, so we don't know what a popup is, we don't know what an icon is. From Windows, we get a zone to update and we get the pixels matching that zone (like any graphics driver). Therefore I'm afraid I am unable to see anything we could do to workaround this third party issue, unfortunately. Kind regards, Alban |
| All times are GMT. The time now is 01:50 PM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2026, vBulletin Solutions, Inc.