You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed that the plugin does not appear to ever log anything to X-Plane's Log.txt file. When the plugin is loaded, X-Plane does mention this in the log, but there is no further information such as the port number it is listening on, if any failures occur while opening up the socket, or when incoming connections are received. If the port is already in use, or some other problem, it is difficult to know why things aren't working.
I could not find any mention of XPLMDebugString in the code, but I have seen logging macros used like this: #define INFO qCritical() << "ExtPlane:" << Q_FUNC_INFO
Do these Qt logging macros end up going anywhere? Do any of these macros work in release mode?
Thanks!
The text was updated successfully, but these errors were encountered:
I think we should investigate using XPLMDebugString for outputting important information to the log. Normal status output should not go there or could even be removed.
I've noticed that the plugin does not appear to ever log anything to X-Plane's Log.txt file. When the plugin is loaded, X-Plane does mention this in the log, but there is no further information such as the port number it is listening on, if any failures occur while opening up the socket, or when incoming connections are received. If the port is already in use, or some other problem, it is difficult to know why things aren't working.
I could not find any mention of XPLMDebugString in the code, but I have seen logging macros used like this: #define INFO qCritical() << "ExtPlane:" << Q_FUNC_INFO
Do these Qt logging macros end up going anywhere? Do any of these macros work in release mode?
Thanks!
The text was updated successfully, but these errors were encountered: