Hi. Thanks for the reply. So it's not an error - just a built in notification. May have to use VNC to connect to this specific server then - it's a VPS and has no physical keyboard/mouse and the overlay is in the way of the notification area which gets in the way of some items/functions. Thanks for the info.
Hi there. Running Windows Server and doing a remote connection. I realize that sometimes there is an overlay that either doesn't go away or embeds itself to the CTRL+ALT+DEL screen. Please see the screenshots attached for more details. I will try with the new version and update.
*EDIT* Confirming that issue exists with beta version as well.
Edited:Carlos Thomas - Aug 02, 2018 11:33:30 pm EDT
Hi there. Great work so far - keep it up! Hoping to see a "close to tray" option later on. The minimize to tray is very useful, but sometimes I forget and hit close when connected and then have to start over. Maybe in the pipeline?
On that note, there was a suggestion by another user about a roadmap. While there are a number of features that we'd like to see, there are probably some that are a priority for your team currently. Maybe as another option - aside fr om specifying which areas you're focusing on now - you could have a thread wh ere persons voice the features they'd like, then run a poll to see which one customers would want you to work on most. Then you prioritize that alongside what you're working on. Just a thought.
All keys function fine - but I was unable to type regular text without holding SHIFT on my end due to CAPS LOCK being on at the remote end. Originally this was found out when setting a password - I just checked it again within a text document and realize that turning on the CAPS LOCK on my end effectively turns it off on the other end. Strangely though, when I was putting in the password and holding SHIFT from my end it was still putting in capital letters. Not sure why. Is there a way to bind the keyboards at both ends or give the priority to mine? By binding I mean ensuring that whichever lock keys (caps, scroll, num) would synchronize on both machines.
Thanks again for your quick response. Looking forward to hearing back from you.
Hi there. Seeing that this is in the pipeline and wondering if there's any update on this so far? Having the logs for each outgoing connection - and the possibility to attach notes - would be great for billing purposes.
Hi there. Apologies for the multiple threads - need to separate the issues and requests. Again - thanks for the work you've done so far - keep it up! Excellent product!
So I noticed connecting from a W7 desktop to a W7 laptop that the remote keyboard takes priority even when you lock remote input. The "CAPS LOCK" key was on remotely and nothing I did locally would override it. Any thoughts on how this could be fixed? Am I overlooking an option?
Thanks again for the info. Will test and get back to you.
*EDIT* Legacy capture mode did not work on the Atom netbook with W10. Will do testing on the tablet and on the desktop then post back the results.
*EDIT* Tested on Microsoft Surface Pro with Windows 8 Pro / i5 CPU. Same issue as with Asus X205T with Windows 10 Home / Atom CPU. Pushes system back to login/lock screen and doesn't turn black at all. Will test with a desktop running Win8/10 between now and next week and post the findings.
Edited:Carlos Thomas - Jun 01, 2018 3:52:03 pm EDT