Hello,
I am working on application to read and write data in FS X, using SimConnect and VB.NET 2010. I could make my programme run, read data about an aircraft, and display them in a form. All this worked well, and still works on the programme compiled in an .exe application.
Now, I am stopped because what was working yesterday does work anymore. The same form and class are now trapped into a loop :
Protected Overrides Sub DefWndProc(ByRef m As Message)
' Simconnect client will send a win32 message when there is a packet to process. ReceiveMessage must be called to
' trigger the events. This model keeps simconnect processing on the main thread.
If m.Msg = WM_USER_SIMCONNECT Then
If fsx_simconnect IsNot Nothing Then
fsx_simconnect.ReceiveMessage()
End If
Else
MyBase.DefWndProc(m)
End If
End Sub
It seems that this sub keeps waiting for a message from win32, having the value &h402. This value never appears, and the sub loops forever. Why ? Yesterday it worked. I restarted the PC 2 times, I checked several things, and I found nothing.
What's happening ?
Jean-Paul
I am working on application to read and write data in FS X, using SimConnect and VB.NET 2010. I could make my programme run, read data about an aircraft, and display them in a form. All this worked well, and still works on the programme compiled in an .exe application.
Now, I am stopped because what was working yesterday does work anymore. The same form and class are now trapped into a loop :
Protected Overrides Sub DefWndProc(ByRef m As Message)
' Simconnect client will send a win32 message when there is a packet to process. ReceiveMessage must be called to
' trigger the events. This model keeps simconnect processing on the main thread.
If m.Msg = WM_USER_SIMCONNECT Then
If fsx_simconnect IsNot Nothing Then
fsx_simconnect.ReceiveMessage()
End If
Else
MyBase.DefWndProc(m)
End If
End Sub
It seems that this sub keeps waiting for a message from win32, having the value &h402. This value never appears, and the sub loops forever. Why ? Yesterday it worked. I restarted the PC 2 times, I checked several things, and I found nothing.
What's happening ?
Jean-Paul

