Bug Tracker – Bug 1174

Include a user-writeable WAD path by default.

Last modified: 2016-09-16 00:29:58 CDT
Bug 1174 - (ARRAY(0x550cb88)) Include a user-writeable WAD path by default.
(ARRAY(0x550cb88))
Include a user-writeable WAD path by default.
Status: NEW
Product: Odamex
Classification: Unclassified
Component: Launcher
0.7.x
All Linux
: P1 enhancement
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2016-04-20 04:24:29 CDT by 166291
Modified: 2016-09-16 00:29 CDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description 166291 2016-04-20 04:24:29 CDT
Currently when using odalaunch it defaults to either the current directory or the installed location for WAD paths. On systems where the installed location is read-only or not otherwise writeable by the user, neither options fare out well and require manual configuration to have something consistent.

I've patched my version of odalaunch to include ~/.odamex as the first directory so WADs can be downloaded and put there without trouble, and my DOOMWADPATH specifies where read-only WADs can be found. This is consistent and predictable as opposed to wherever I first run odalaunch from.

This bug affects systems where the user cannot write to the install directory but still want odalaunch to work without spewing WADs all over their home directory.
Comment 1 Mike Wood 2016-07-24 16:35:46 CDT
The default would have to be something cross-compatible and should be obtained through the wxwidgets API. Some candidates:

wxStandardPaths::GetDocumentsDir() [﷒0﷓] - Returns the user's Documents path.

wxStandardPaths::GetUserDir(Dir userDir) [﷒1﷓] - With Dir_Downloads parameter value, returns the user's Downloads path.

Thoughts are welcome.