Added a note about using the console application to view the log file. authored by Kevin Meaney's avatar Kevin Meaney
......@@ -146,7 +146,7 @@ To output the value returned from running smig, you add echo $? on the line foll
Particularly during script development, it is necessary to be able to debug your smig commands. Checking error codes as described above is essential, but there are other things you can do.
MovingImages also has a log file. The log file is in the ~/Library/logs directory and is called "U6TV63RN87.com.yvs.MovingImagesAgent YYYY-MM-DD HH-mm.log" where the "YYYY-MM-DD HH-mm" part of the file name is the date and time when the log file was first created. Output is sent to the log file when something goes wrong whilst creating filter chains, rendering filter chains or drawing shapes and images. There is usually multiple messages sent for each problem, the first message outputs the object where something is missing and then each following message provides greater context within which the problem occurred until finally you get what I call railroad tracks. A line of equal signs like so "======================================" which means the end of messages relating to this particular problem.
MovingImages also has a log file. The log file is in the ~/Library/logs directory and is called "U6TV63RN87.com.yvs.MovingImagesAgent YYYY-MM-DD HH-mm.log" where the "YYYY-MM-DD HH-mm" part of the file name is the date and time when the log file was first created. The easiest way to view the log file is to use the Console application. Output is sent to the log file when something goes wrong whilst creating filter chains, rendering filter chains or drawing shapes and images. There is usually multiple messages sent for each problem, the first message outputs the object where something is missing and then each following message provides greater context within which the problem occurred until finally you get what I call railroad tracks. A line of equal signs like so "======================================" which means the end of messages relating to this particular problem.
Currently the remaining debugging support relates to the bitmap context and draw element commands. You can send a "-showwindow YES" "doaction" message to a bitmap context base object. The displayed window is a palette window that cannot be moved or resized. The only way to get rid of the window is to send a "-showwindow NO" "doaction" message. On a single display computer the window will cover a maximum of the bottom right quarter of the display, and on a computer with multiple displays the window will be displayed on the screen which currently does not have a window which has focus. While the window is displayed all drawing commands sent to the bitmap context will also be displayed in the shown window.
......
......