zfi
commented
7 years ago The execution path for Windows is unique in some areas of the code. Sine the initial emphasis for the detailed logging was to identify gross logic errors in the MacOS path, very little Windows-specific code was given the logging treatment. This certainly can be corrected but it's not a priority.
The double logging in the Linux/MacOS code paths is likely caused by defining more that one logger. The log events are sent to all listening loggers, so there must be two loggers listening to the events.
On Windows, there is a definite difference in behavior in logging in comparison to what is logged in Mac.
The next two log listings are from the same version (v0.5.4) of BlocklyPropClient, performing the same steps, downloading the same BlocklyProp project to a Propeller, and all done within about 1 minute of time.
On Windows, there are no repetitive logged events for COM port enumeration, no indication that the Connect button was clicked (no service starting messages), no logged activity of download processes being performed, and no logged activity of debug sessions:
On Mac, there are repetitive logged events for COM port enumeration (don't think that's ideal, but it shows that there's activity), shows logged activity of download processes being performed, and also logged activity of debug sessions: