Forced to run in full screen

desktop icons are unclickable

from Stardock Forums

Using two Windows10 22H2 computers. Main computer is using dual monitors wth main monitor at 2560x1440 on 27" monitor. Remote computer is headless. I has no mouse or keyboard connected and using a HDMI dummy plug running at 2560x1440 resolution as well. 

When I connect to the remote computer I have to put Multiplicity 4 in full screen mode for all the icons on the remote computer to be clickable. If I do not and MC is using the vertical scroll bar to move the remote desktop up and down then the icons on the lower part of the remote computer are not clickable. That is because the mouse cursor has to be positioned a row lower down on the remote desktop to have the hightlight square wind up on the correct icon. 

If I put the remote screen into full screen mode there is no issue with the lower desktop icons.  Anyone else see this type of behavoir?

multiplicity
4,352 views 11 replies
Reply #1 from Stardock Forums Top

Hello,
I have forwarded your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

Reply #2 from Stardock Forums Top

Well it is now January 6th and I am still struggling with this. I had the misfortune of having to minimize the remote window for the computer so that I could get back to my own computer screen. When I tried to maximize the remote computer screen Multiplicity would NOT hide the top bar and it appeared that the taskbar was double height. The result was that none of the lower screen clicks on the remote computer were registering at the proper location on the remote computer. They were a row above where the cursor was. This included the Start button so I had to use the power button on the remote computer to close Windows10 and power the system off. 

Ashes of the Singularity II
Reply #3 from Stardock Forums Top

Hello,
I have forwarded your problem again to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

 
 

 

 

Reply #4 from Stardock Forums Top

If you click on the sprocket for any given KVM connection, does the 'Adjust for DPI differences' or any other setting there help resolve this?

Sean Drohan
Stardock Product Lifecycle Manager

Reply #5 from Stardock Forums Top

Quoting sdrohan, reply 4

If you click on the sprocket for any given KVM connection, does the 'Adjust for DPI differences' or any other setting there help resolve this?

Sean Drohan
Stardock Product Lifecycle Manager
End of sdrohan's quote

Adjust for DPI differences makes no difference. Nor does any of the other options that I can see. Both the remote screen and the Multiplicity computer screen resolutions are identical. 2560x1440 on a 27" monitor.

The only way I can KVM into the machine and be able to click on pop up notifications, taskbar icons or icons in the lower portion of the remote desktop is if I run multiplicity in FULL SCREEN mode and make darn sure that the option Always Show Tab Bar is DISABLED> Otherwise I can not click on any of the icons in the lower portion of the remote computer or the taskbar icons. 

Heaven forbid if I need to get to my main computer desktop. I have to go out of fullscreen mode. Then minimize the Multiplicity KVM window with the remote computer screen, and do what I need to do on my main computer. If I want to go back to the remote computer I have to restore the Multiplicity screen then go into the gear icon and select fullscreen from the gear pulldown menu.  

If there is a vertical scrollbar at all for the remote computer it causes problems with not being able to click on icons in the lower portion of the remote computer desktop. This includes the taskbar of the remote computer. Those icons are not clickable. I also noticed that if there is a vertical scrollbar for the remote computer then the taskbar on the remote computer appears like it has been manually resized height-wise. There is white space below the taskbar icons. 

Reply #6 from Stardock Forums Top


Using two Windows10 22H2 computers. Main computer is using dual monitors wth main monitor at 2560x1440 on 27" monitor. Remote computer is headless. I has no mouse or keyboard connected and using a HDMI dummy plug running at 2560x1440 resolution as well. 
End of quote

If at all possible for a test.  If it had an actual monitor connected to a headless one, does it then function as expected?

Sean Drohan
Stardock Product Lifecycle Manager

Reply #7 from Stardock Forums Top

Quoting sdrohan, reply 6


If at all possible for a test.  If it had an actual monitor connected to a headless one, does it then function as expected?

Sean Drohan
Stardock Product Lifecycle Manager
End of sdrohan's quote

I do not have a spare monitor capable of 2560x1440 but I do have one that can do 1920x1080. So I lowered the resolution on my main computer with the 27" monitor to 1920x1080, and hooked up the monitor to the remote computer. It exhibited the same issue UNTIL I selected Stretch. That caused the vertical scroll bar to disappear, the size of the desktop of the remote computer shrunk slightly in size and 2 black vertical bars appeared on either side of the remote desktop.   I was able to click on the icons lower down on the desktop as well as the icons in the remote desktop taskbar.

I then hooked up the dummy monitor plug to the remote computer, reset my main computer back to the 2560x1440 resolution and KVM'd to the remote computer. With Stretch enabled the icons were clickable and no vertical scrollbar. As soon as I switched to 1:1 the vertical scrollbar and click issue appeared.  

To me Stretch implies enlarging the item/view on the screen not shrinking it. With Stretch enabled Multiplicity is usable without having to go into full screen. 

Reply #8 from Stardock Forums Top

This bleeping issue is happening again. I have no keyboard use on the computer with the dummy HDMI adapter. When the password field has focus, clicking on the other account on the login screen does nothing. The keyboard is useless. None of the keys work. 

 

The IP address changed. Once I saved the configuration information, the Multiplicity saved the changes, I regained the use of the mouse and keyboard. The software really needs to indicate that it can not connect, rather than displaying a video signal and only then preventing the mouse and keyboard from working due to IP address issues. 

Reply #9 from Stardock Forums Top

Quoting Frustrated99, reply 8

This bleeping issue is happening again. I have no keyboard use on the computer with the dummy HDMI adapter. When the password field has focus, clicking on the other account on the login screen does nothing. The keyboard is useless. None of the keys work. 

 

The IP address changed. Once I saved the configuration information, the Multiplicity saved the changes, I regained the use of the mouse and keyboard. The software really needs to indicate that it can not connect, rather than displaying a video signal and only then preventing the mouse and keyboard from working due to IP address issues. 
End of Frustrated99's quote

So you are working again, yes?

Sean Drohan
Stardock Product Lifecycle Manager

Reply #10 from Stardock Forums Top

Yes but it took me 30+ mins to figure out what the issue was. I changed settings not to use the IP address.  Probably will avoid setting the use of IP addresses if the device is not using a hard coded IP. Whether it will work properly the next time I need it to work is debatable. 

Reply #11 from Stardock Forums Top

Quoting Frustrated99, reply 10

Yes but it took me 30+ mins to figure out what the issue was. I changed settings not to use the IP address.  Probably will avoid setting the use of IP addresses if the device is not using a hard coded IP. Whether it will work properly the next time I need it to work is debatable. 
End of Frustrated99's quote

You should not use the IP option unless the machine has a static IP.

Otherwise it will not work when the IP address changes.