WCmore's LogAndTrace - Revision history

WCmore: /* Customizable Logs */

2020-09-11T04:52:00Z

‎Customizable Logs

2020-09-04T04:30:42Z

2020-09-04T04:29:56Z

2020-04-29T17:34:25Z

2020-04-28T23:58:46Z

2020-04-28T23:57:54Z

2020-04-17T03:48:35Z

‎Summary

2020-03-13T06:41:47Z

2020-03-10T05:06:12Z

2020-03-10T05:05:32Z

← Older revision		Revision as of 04:52, 11 September 2020
Line 99:		Line 99:

	[[File:LogAdvanceColors2.png\|none]]		[[File:LogAdvanceColors2.png\|none]]
		+
		+	Dark colors look best... (unless you are using a custom CSS)

	{{WCmoreTOC}}		{{WCmoreTOC}}

@@ Line 96: / Line 96: @@
 [[File:LogAdvanceColors.png|none]]
-... which spits out this:
+... returns the following log:
 [[File:LogAdvanceColors2.png|none]]
 {{WCmoreTOC}}

← Older revision		Revision as of 04:29, 4 September 2020
Line 89:		Line 89:

	This can be helpful to make certain events '''stand out''' in the logs...		This can be helpful to make certain events '''stand out''' in the logs...
		+
		+	-----
		+
		+	If you are willing to write a bit of extra code, then nearly any color can be achieved. For example, this snippet of code:
		+
		+	[[File:LogAdvanceColors.png\|none]]
		+
		+	... which spits out this:
		+
		+	[[File:LogAdvanceColors2.png\|none]]

	{{WCmoreTOC}}		{{WCmoreTOC}}

@@ Line 35: / Line 35: @@
 Once "Trace" is turned on, you will notice extra numbers in your green snapshot that aligns with the Condition #'s in your log.  ''(As highlighted below)''
-[[File:TraceAndLog.jpg|none]]
+[[File:TraceAndLog2.jpg|none]]
 This makes is easy to follow along, line by line, and see right away what line of code caused an error.
@@ Line 78: / Line 78: @@
 == Customizable Logs ==
-* You can manually add nearly anything to the log, as seen on line 20 [[WCmore's_LogAndTrace#Summary|above]].  ''(Manual logs will always appear, even if Logging Level is set to None)''
+* You can manually add nearly anything to the log, as seen on line 22 [[WCmore's_LogAndTrace#Summary|above]].  ''(Manual logs will always appear, even if Logging Level is set to None)''
 The command appears as "Log to console", and you can select one of five log "Types".

← Older revision		Revision as of 23:58, 28 April 2020
Line 38:		Line 38:

	This makes is easy to follow along, line by line, and see right away what line of code caused an error.		This makes is easy to follow along, line by line, and see right away what line of code caused an error.
		+
		+
		+
		+

	== Personal Thoughts ==		== Personal Thoughts ==

@@ Line 64: / Line 64: @@
 * On that note, if you edit a piston, you may as well Clear your logs, and run your test again.  ''(the old logs no longer apply)''
 * Once a piston has been rock solid reliable for awhile, I often reduce Logging level to Minimum or None
 * If Logging Level is None, then editing/saving a piston will automatically '''clear''' the logs.
 * If Logging Level is anything '''except''' None, then editing/saving a piston will '''preserve''' the logs.
 * If your piston is massive, and saving is difficult due to lack of space, sometimes turning the Logs to None & pressing Clear can help.
 {{WCmoreTOC}}

@@ Line 33: / Line 33: @@
 == Summary ==
-Once "Trace" is turned on, you will notice extra numbers in your green snapshot that aligns with the Condition #'s in your log.  ''(As seen in this sample piston)''
+Once "Trace" is turned on, you will notice extra numbers in your green snapshot that aligns with the Condition #'s in your log.  ''(As highlighted below)''
 [[File:TraceAndLog.jpg|none]]
 This makes is easy to follow along, line by line, and see right away what line of code caused an error.
 == Personal Thoughts ==