Jeff0S
commented
10 years ago From swstim on April 17, 2010 16:33:44
Hmm...
To be honest I would prefer the Cockos way of enabling/disabling feature from the installer:
Put larger sorts of feature sets that you want to be optional separate into a separate .dll file.
So, if you want the RME Totalmix stuff separate, I would make a new vcproj that creates a reaper_totalmix.dll.
As for simple actions like "shrink selected items" that don't add too much to the list or code space I say leave 'em in!
Right now I like just having a section in the reaper.ini file. This way the SWS settings are saved the same was as Reaper's settings. By default they're global to all installations, but if you don't like it that way, you can dump reaper.ini into your reaper.exe directory. I could put the logic to find the correct reaper.ini path into the installer but that seems like overkill to me. Another note along these lines, I like to respect the OS's belief that INI files shouldn't be in the same dir as the EXEs, esp because of Vista/Win7 style permissions.
Anyway, just my opinion, feel free to disagree and do whatever you like!
From Atrabili...@gmail.com on April 16, 2010 10:11:52
Just a few ideas I had in mind:
I'm planning a new set of actions for the RME Totalmix app that comes with Fireface audio interfaces. For non-Fireface users this will just pollute the action list.
Same thing with my own "shrink selected items: -x samples" actions. Most Reaper users don't need those either.
Any thought?
Padre
Original issue: http://code.google.com/p/sws-extension/issues/detail?id=116