Comprehensive Debug log

[perdrix52]

Feature Request:

1. Add a Debug Log function to DSS v4.x
2. Output ALWAYS GENERATED - so User doesn't have to re-run a problematic Session with Debug-Log=ON and hope for the same outcome as the original instance
3. Output Filename Timestamp-Coded and generated to one of a limited selection of Directory choices - Documents\DSS; or the Directory of the current DSSFilelist
4. Debug File contain readily human-readable format - CSV or JSON or simple XML - with data including timestamped rows of Terse-but-Understandable data
5. Debug File contain all Current Settings (superset of that recorded in the DSSFilelist file) accurate as of start of Register/Stacking action
6. Debug File contain a recap of the Host PC Resources available at start of Register/Stacking action
7. Debug File contain details for all the Filesets and Images actively selected for the current Register/Stack/Render including any pre-existing Registration data if not Register-already-registered-pictures
8. Debug File contain a pertinent recap of the internal actions performed per-Image and per-Action, as well as a recap of the resulting Data Values
9. Debug File Writes be performed in a most-conservative fashion (Write/Flush/Close and/or strong Exception Handlers)
10. New Debug File be started upon Clear-Filelist and Open-Filelist
11. Add "Report Issue" Support Feature (Menu Item in Help Menu)
12. Provide concise Step-by-Step instructions for reporting an Issue to DeepSkyStacker groups.io
13. Provide suggestion of how to Title the Topic to best gain Support attention
14. Provide DirectoryName for location of Debug File
15. Provide generic instructions for uploading Debug File to a Cloud File Share such as DropBox, OneDrive, etal (assume that Admin doesn't want these Files uploaded directly to Group.io if Forum License is based on Space Usage)
16. Provide "Debug File Package" generation support (consider generating a Compressed File Package - .zip or other OpenSource format), if multiple files (Debug File, DSSFilelist, AutoSave, minimal set of Lights, etc) are regularly part of the Support regimen

This is a Large Ask. With significant details. !!!

[perdrix52]

Maybe write the trace file to a "known location" e.g. Documents/DeepSkyStacker and generate a unique fn e.g. DSSTrace_yyyymmdd_hhmmss.log and write a filelist file to same location at start of registering/stacking?