I have thought of something else. When I did the remote upgrade, I picked the generic host install msi file that I downloaded from the Beta page. Could that be the reason for the settings to be erased - because I didn't customize the msi installer first?
Certainly, not. Quite the contrary - if you use the "vanilla" Host during upgrade, the Host settings should be intact.
I assumed that the upgrade would re-use the existing config from the Host I was upgrading.
The only setting that sometimes causes issues in apps for me is the custom scale factor I have set (175%).
Thanks for letting us know. Yes, scaling might cause this issue, although I've just set 175% scaling and I still have a 1-row toolbar, but there could be other factors in effect.
We will test this further and see if we can reproduce the issue, although I'm not sure if we can provide any fix. Program windows and their standard controls - especially their size/fonts are mostly governed by the operating system rather than the application itself. So it's the OS that dictates how windows and controls look like and behave.
This frequently causes windows and dialog boxes to have shifted or cut off text or buttons in apps that do not account for the scaling. I know I'm a unique case in this regard.
No problem! We may not test the program at all scaling values or resolutions (that would significantly complicate the testing process and slow down development) but at least we have a chance to receive reports right away from real users like yourself.
I'm using my own self-hosted Server. In the Server interface, I see all my Hosts listed, with their external IP's correctly listed. In my Viewer, however, the Last IP column displays the IP address of the self-hosted Server instead of the actual WAN IP of the Host. The exception being the Hosts that are on the same LAN and are being connected to directly.
That is absolutely correct. Hosts that communicate with the Viewer through the server rather than directly are "invisible" to the Viewer, so to say. Their IP address is only known to the server.
One other related observation. One Host that has been upgraded to latest beta, 22.214.171.124, and is the same Host that the Viewer is running on, is displaying 169.254.13.154 as the Last IP.
It all depends on your specific configuration, your network adapters, settings etc. You may have multiple network interfaces and apparently 169.254.x.x is one of those.
Thanks for your reply. The Viewer is a Win10 Pro machine, and the Host is a Windows 7 Pro machine. I've emailed the logs and the screenshot to the support address.
Well received, thanks. I've forwarded the logs and other information to our development to see what they can say about this. Since remote upgrade from version 126.96.36.199 works ok in our tests, it could be something with specific PC configuration, security settings or something else.
Regarding the two-row toolbar - your window chrome (frame) looks quite unusual. Do you have any theme pack or something else that modifies default Windows window layout, controls etc.?
I'm a little hesitant about upgrading the Server module. With my luck, something will go wrong and all my Hosts will become inaccessible.
Do you have another computer to install the server on?
I have another Host that I can test upgrading with, a Windows 10 laptop that is right next to me. Do you recommend trying to upgrade just by running the .msi directly on the laptop, or try upgrading using the Tools > Upgrade outdated Hosts tool in the Viewer?
Actually, both should work. The Remote Install tool is just for convenience. You can, of course, run manual installation if it's possible (i.e. you can physically access the computer).