search

osoko / retroremakes-framework

Automatically exported from code.google.com/p/retroremakes-framework
0 stars 0 forks source link

Using rrEngineInitialise() before rrUseExeDirectoryForData() causes ini files not to be created/loaded #26

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. in your source, put rrEngineInitialise() before rrUseExeDirectoryForData()
2. compile, see no ini file appear

suggestion: call rrUseExeDirectoryForData() in rrEngineInitialise()

Original issue reported on code.google.com by wiebo.de.wit on 29 Sep 2010 at 11:41

GoogleCodeExporter commented 9 years ago

Original comment by wiebo.de.wit on 29 Sep 2010 at 11:42

GoogleCodeExporter commented 9 years ago

Original comment by wiebo.de.wit on 29 Sep 2010 at 11:42

GoogleCodeExporter commented 9 years ago 
additional note: the virtualgamepads example has this problem.

Original comment by wiebo.de.wit on 29 Sep 2010 at 11:43

GoogleCodeExporter commented 9 years ago 
If rrUseExeDirectoryForData() is not called before rrEngineInitialise() then 
the directory used for log/ini files is the OS-specific user directory.  On 
windows this should be %APPDATA%.  This should be the default behaviour, as 
otherwise we can run into issues with UAC on Windows if the eventual 
application is installed in Program Files.

Original comment by mu77...@gmail.com on 29 Sep 2010 at 11:59

GoogleCodeExporter commented 9 years ago 
Just to clarify, the directory used on Windows if rrUseExeDirectoryForData() is 
not used will be %APPDATA%\ProgramName, so the VirtualGamepads example will 
write data to %APPDATA\VirtualGamepads.

rrUseExeDirectoryForData() should really only be used for testing/development 
purposes.

Original comment by mu77...@gmail.com on 29 Sep 2010 at 5:05

GoogleCodeExporter commented 9 years ago 
Wow! I never knew that. Thanks for clearing that up.

Original comment by wiebo.de.wit on 29 Sep 2010 at 5:49