reaper-oss / sws

The SWS extension is a collection of features that seamlessly integrate into REAPER, the Digital Audio Workstation (DAW) software by Cockos, Inc
https://www.sws-extension.org/
MIT License
455 stars 85 forks source link

Strange location of the action help INI file #191

Closed Jeff0S closed 10 years ago

Jeff0S commented 10 years ago

From jeffos...@gmail.com on September 26, 2010 11:39:24

from Susan G: http://forum.cockos.com/showpost.php?p=588951&postcount=742 ___

I just noticed that my default action_help .ini file is named differently and stored in a different location from what it says on your site:

Quote: S&M_Action_help_en.ini (in REAPER's default resource directory, with other ini files).

Mine's \Users{username}\AppData\Local\VirtualStore\Program Files\REAPER\Plugins\Action_help_en.ini

Maybe big whoop, but shouldn't it be in \Roaming rather than \Local? That's where all my other REAPER .ini files are, and what my resource path points to.

Thanks again-

-Susan

Edit: It just occurred to me that maybe it was written there during one of my beta installations, in which case I can just delete it and a new one will be created in the right place(?). I'll try that.

Edit #2: Nope, I deleted it & nothing saved, so I reinstalled the exts and it was put in the same \Local\Virtual Store folder, still as "Action_help_en.ini". (Yes, I know we can define our own. )

_____ http://forum.cockos.com/showpost.php?p=589458&postcount=747 Hi Jeff-

Quote: Originally Posted by Jeffos
Susan, is this path consistent with "ACTION_HELP_FILE=" in your S&M.ini ? If so, this is "normal": most probably due to the beta phase (I changed that default file/location between beeta #5 and #6)

No, the path in that file is "D:\Program Files\REAPER\Plugins\".

Code: [ACTION_HELP] PATH=D:\Program Files\REAPER\Plugins\Action_help_en.ini [NOTES_HELP_VIEW] ACTION_HELP_FILE=D:\Program Files\REAPER\Plugins\Action_help_en.iniMy Action_help_en.ini file is actually in "D:\Users\SMG\AppData\Local\VirtualStore\Progr am Files\REAPER\Plugins", even after a reinstall.

That's the only such file on my whole system, so it's not a question of pointing to a duplicate or anything.

Original issue: http://code.google.com/p/sws-extension/issues/detail?id=191

Jeff0S commented 10 years ago

From jeffos...@gmail.com on September 26, 2010 03:02:24

Thanks for all the details, Susan! It indeed begins to smell like a bug, but I can't reproduce and, given the code, I don't understand..

For the moment, here's what I think (well.. "hope"): this stange "\Users{username}\AppData\Local\VirtualStore\Program Files\REAPER\Plugins\Action_help_en.ini" has been created at some point, for some (beta phase or user operation) reasons. It's not used anymore but still there. The real current one is indeed the one specified in the S&M.ini file: "D:\Program Files\REAPER\Plugins\Action_help_en.ini"

Susan, in order to verify, can you answer these Qs:

=> re-start REAPER, enter a random action help where is it saved ? (it should be S&M_Action_help_en.ini, in REAPER's default resource directory, with other ini files).

Jeff0S commented 10 years ago

From jeffos...@gmail.com on September 26, 2010 03:21:13

Ok, I re-read: "That's the only such file on my whole system, so it's not a question of pointing to a duplicate or anything."

So, can you just clean-up your S&M.ini file as described above and let me know. Also I see "D:..." => is REAPER indeed installed there, or was it installed there at some point?

Jeff0S commented 10 years ago

From hooey...@gmail.com on September 26, 2010 12:42:13

Hi Jeff-

Ok, I removed those lines from S&M.ini and deleted my action_help file, ran REAPER, and added a test note. Now I have a "D:\Users\SMG\AppData\Roaming\REAPER\S&M_Action_help_en.ini" file, and that's where the test note was stored.

So it all looks good. :)

Quote: Also I see "D:..." => is REAPER indeed installed there...? Yes.

Thanks!

-Susan

Jeff0S commented 10 years ago

From jeffos...@gmail.com on September 26, 2010 23:47:06

Cool! Closing.. (I'm not sure of what happened here, we'll re-open this issue if needed..)

Status: NoChanges