Fix logged in state, logging in logic

- Relocated the Login() call back into the UPS class to keep logic and exceptions out of the WinNUT form (fixes connected notifications not appearing on reconnect)
- Properly unset logged in flag when disconnecting. From my limited testing, the NUT server does not care how you disconnect from it - you'll always be able to log back in.

Author: gbakeman

WinNUT_V2/WinNUT-Client/WinNUT.vb

@@ -402,10 +402,6 @@ Public Class WinNUT
         LogFile.LogTracing("Connection to Nut Host Established", LogLvl.LOG_NOTICE, Me,
                            String.Format(StrLog.Item(AppResxStr.STR_LOG_CONNECTED),
                                          upsConf.Host, upsConf.Port))
-
-        If Not String.IsNullOrEmpty(upsConf.Login) Then
-            UPS_Device.Login()
-        End If
     End Sub
 
     Private Sub ConnectionError(sender As UPS_Device, ex As Exception) Handles UPS_Device.ConnectionError

WinNUT_V2/WinNUT-Client_Common/Nut_Socket.vb

@@ -128,6 +128,8 @@ Public Class Nut_Socket
             Query_Data("LOGOUT")
         End If
 
+        _isLoggedIn = False
+
         If WriterStream IsNot Nothing Then
             WriterStream.Dispose()
         End If

WinNUT_V2/WinNUT-Client_Common/UPS_Device.vb

@@ -144,6 +144,10 @@ Public Class UPS_Device
             Update_Data.Start()
             RaiseEvent Connected(Me)
 
+            If Not String.IsNullOrEmpty(Nut_Config.Login) Then
+                Login()
+            End If
+
         Catch ex As NutException
             ' This is how we determine if we have a valid UPS name entered, among other errors.
             RaiseEvent EncounteredNUTException(Me, ex)