Details
-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
1.4.0
-
None
-
Operating System: Windows 7
Platform: Intel
Description
it seems that after changing to log4net logging some glitches in Minidisplay logging were introduced. e.g.
[2013-04-27 15:04:34,809] [Log ] [MPMain ] [DEBUG] - MiniDisplay.VFD_Control: Vendor ID: {0:X}, Product ID: {1:X}, Version {2:X}1382
[2013-04-27 15:04:36,187] [Log ] [MiniDisplay] [INFO ] - MiniDisplayPlugin.DisplayHandler.Process(): translated line #{0} to "{2}"
I created a patch for 2 files belonging to MiniDisplay VS project - see origin thread
h4. Steps to Reproduce
enable minidisplay (if you don't have one - select "Debug preview form" as type).
enable extensive logging for minidisplay.
[2013-04-27 15:04:34,809] [Log ] [MPMain ] [DEBUG] - MiniDisplay.VFD_Control: Vendor ID: {0:X}, Product ID: {1:X}, Version {2:X}1382
[2013-04-27 15:04:36,187] [Log ] [MiniDisplay] [INFO ] - MiniDisplayPlugin.DisplayHandler.Process(): translated line #{0} to "{2}"
I created a patch for 2 files belonging to MiniDisplay VS project - see origin thread
h4. Steps to Reproduce
enable minidisplay (if you don't have one - select "Debug preview form" as type).
enable extensive logging for minidisplay.
Attachments
Issue Links
- links to