Opened 6 years ago
#5103 new defect
Remove disabled readme.txt commandline arguments
Reported by: | elexis | Owned by: | |
---|---|---|---|
Priority: | Should Have | Milestone: | Backlog |
Component: | Core engine | Keywords: | |
Cc: | Patch: |
Description
While searching for a command, I stumbled upon these command line arguments which were not documented, only pronounced "disabled". The code for these arguments was disabled and/or removed long ago.
Index: binaries/system/readme.txt =================================================================== --- binaries/system/readme.txt (revision 21630) +++ binaries/system/readme.txt (working copy) @@ -47,13 +47,10 @@ Configuration: Advanced / diagnostic: -version print the version of the engine and exit -dumpSchema creates a file entity.rng in the working directory, containing complete entity XML schema, used by various analysis tools --entgraph (disabled) --listfiles (disabled) --profile=NAME (disabled) -replay=PATH non-visual replay of a previous game, used for analysis purposes PATH is system path to commands.txt containing simulation log -replay-visual=PATH visual replay of a previous game, used for analysis purposes PATH is system path to commands.txt containing simulation log -writableRoot store runtime game data in root data directory Index: source/ps/GameSetup/Config.cpp =================================================================== --- source/ps/GameSetup/Config.cpp (revision 21630) +++ source/ps/GameSetup/Config.cpp (working copy) @@ -139,16 +139,10 @@ static void ProcessCommandLineArgs(const g_Gamma = args.Get("g").ToFloat(); if (g_Gamma == 0.0f) g_Gamma = 1.0f; } -// if (args.Has("listfiles")) -// trace_enable(true); - - if (args.Has("profile")) - g_ConfigDB.SetValueString(CFG_COMMAND, "profile", args.Get("profile")); - if (args.Has("quickstart")) { g_Quickstart = true; g_DisableAudio = true; // do this for backward-compatibility with user expectations }
I propose to remove the arguments and the remaining commented out code entirely, find out what it did and instead write a good ticket if the tasks are still useful.
Note:
See TracTickets
for help on using tickets.