There was an error while loading. Please reload this page.
Merge branch 'master' of https://github.com/ObjectVision/GeoDMS.wiki # Conflicts: # Command-line-options.md
Document that a /L log file now survives a fatal error (GeoDMS 20.18.0) Command-line-options gets a new section, "the log file and fatal errors": log lines are buffered, and until 20.18.0 that buffer was only emptied on an orderly close, so a run that ended fatally lost exactly the messages worth reading. Such a run now ends with a FATAL: block in the log and on standard error, naming the error and the context chain of the failing thread -- for a calculation thread, the item and operation being computed. That block is what a bug report needs. Also records the exit-code change: a Release-build fatal used to end the process with -1073740791 (0xC0000409) and no message; it now ends with 3, the code a Debug assertion already used. An automated run that checks %ErrorLevel% / $LASTEXITCODE keeps working, and now sees an ordinary non-zero code instead of a crash. Both codes are described in the User-Guide-GeoDMS-Run exit-code table. Eventlog notes that this one report deliberately does NOT pass through the eventlog -- it goes down with the application -- so when the GUI disappears without a message, the session log is where the explanation is. Cross-page links use the plain [[label|Page]] form the other pages use; anchored cross-page links appear nowhere else in this wiki, so the sections are named in prose. See GeoDMS issue #1191.
Drop the removed status flags from the tables (GeoDMS #694) /SV /SD /SE /ST /SI /SR no longer exist, so the section listing them as accepted but inert goes, and the GeoDmsRun page no longer names them among the flags that address the GUI. A letter that is not in the table is covered by the section on unrecognised letters. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Keep the command line options page to current behaviour (GeoDMS #694) The section on the six inert status flags explained which GUI once read them, and the GeoDmsRun section carried a note about a /PProjName option that its usage text no longer prints. Neither tells a reader anything about the software in front of them: the six flags are accepted and change nothing, and that is the whole of it. The removed paragraph also named MFC, which the GeoDMS never used. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Document ShowHiddenItems as a configuration setting (GeoDMS #694) The Config Options dialog page described the ConfigSettings/Overridable mechanism generically - "all string parameters are presented in this view" - without saying that any name in there means something to the GeoDMS itself. ShowHiddenItems is the first that does, so the page gains a table for those, plus the two things a reader has to know about it: the value is applied to the session rather than written to the registry, and /SA or /CA overrules it. Also documents the Session tick box, which is what makes an override last for one session instead of becoming the machine's setting - the difference that decides whether reopening a project brings its own value back. Cross-referenced from the Show hidden items option in GUI Options dialog and from the /SA row and the per-run section of Command line options. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Correct the /L trace-log claim on Command-line-options /L switches on the TraceLogFile status flag in GeoDmsRun only; the GUI just opens the named log and keeps the trace log as its own setting under Local machine options. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Document the command line options of both executables (GeoDMS #694) New page Command-line-options: the arguments of GeoDmsGuiQt.exe and GeoDmsRun.exe, and one authoritative table of the /S<X> and /C<X> status flags, taken from RTC_ParseRegStatusFlag rather than from memory. Things it settles that were not written down anywhere: - /SA and /CA switch admin mode -- showing or hiding items configured with IsHidden -- from the command line. That is the workaround for #694 until a configuration-level setting exists; - /SV /SD /SE /ST /SI /SR still parse, but nothing in the Qt GUI or in GeoDmsRun reads those flags any more. They are MFC leftovers; - an unrecognised letter does not abort the run, it warns and carries on; - the flags override the registry for one run only, but pressing OK in the GUI Options dialog writes them back, so a command-line value can become the user default by accident; - the order the parser expects, and what happens to an option given out of turn: rejected before the configuration file name, silently swallowed as an item name after it. The status-flag table in User-Guide-GeoDMS-Run keeps the batch-relevant rows and refers to the new page for the rest, so there is one place to maintain. Its /PProjName note moves along, now that the phantom option has been removed from the executable's usage text. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>