Bug reports

VarAC doesn't seem to be able to locate its own home directory while run from Wine (it ends up putting its config files in the user's home directory): VarAC's .conf & .ini files are housed in the VarAC directory (in the ~/.wine/ folder), but the .ini files there don't get used. VarAC also then creates brand new .conf & .ini files inside of ~/. (aka /home/user/.) that VarAC is actually reading/writing to. VarAC still functions well, but it makes the initial installation of VarAC not very intuitive for users (users have to know default ports for applications) and it also causes error messages to pop up until the config files are all in the user's home directory. I've tried making workarounds for this using AutoHotKey and sed in an installer script, but I can't seem to work around the config file problem easily/elegantly at the moment. VarAC accidentally putting its config files in the /home/user/ directory (instead of its own ~/.wine/drive_c/VarAC program folder) is kind of messy for users and could lead to some users accidentally deleting their settings files without realizing. This bug could also be related to a minor bug where VarAC seems to only run if invoked from outside its own program directory (for example, in the terminal, if I go to the program directory and try to run VarAC then it doesn't open, but if I go up one directory and run it then it opens).