Difference between revisions of "Talk:Completed: Proposal Binding Effects to Hot-Keys"

From Audacity Wiki
Jump to: navigation, search
(Moved relevant discussion points from forum thread that initiated this proposal)
 
(trimmed the discussion - removed irrelavancies)
Line 31: Line 31:
 
'''Edgar 2Nov11:'''  
 
'''Edgar 2Nov11:'''  
  
Not hard at all--that is my ultimate goal. I spent over 3 hours today on one pesky bug only to realize I was working from a codebase which had two built-in versions of Generate Silence (the original and my own custom version). It will take a few hours to strip out all the new code and port it to SVN HEAD. If it rains tomorrow (as predicted) I might get that done so I can get back to working on the solution.
+
Not hard at all--that is my ultimate goal.  
  
 
I now have the ON/OFF switch working so the user may leave effects in the plug-ins folder and turn menu items On/Off even for built-in effects. Next will be to add keyboard shortcuts and categories will come last.
 
I now have the ON/OFF switch working so the user may leave effects in the plug-ins folder and turn menu items On/Off even for built-in effects. Next will be to add keyboard shortcuts and categories will come last.
 
Again, unless you compile your own Audacity, you will never see anything more than screen shots <grin>. I could compile a custom version for you but that is fraught with danger for you--you would be trusting me completely--something I discourage in general. If I post source, you (and the others here) may inspect the code before compiling/using it.
 
  
  

Revision as of 16:10, 31 December 2011

Relevant discussion points from forum thread that initiated this proposal

Edgar 1Nov11:

Effects mapping to keys.png

This is real code but only built-in Effects are considered and only the GUI is implemented at this time. I have some ideas about how to install the shortcuts on the menu. I realize that post-2.0 the Developers have plans to add the Effects plug-ins to the Commands Manager – this should make managing their shortcuts a lot easier.

My interim solution allows the user to turn any Effect on or off in the menu, select whether the Effect dialog opens showing the default values or the most recently used values and, obviously, allows the association of the keyboard shortcut. It also creates a separate Preferences page – the Keyboard page is already very long.

This Preference page might also be an appropriate venue for assigning a category to an Effect.


Steve Daulton 1Nv11:

That looks really interesting Edgar.


Edgar 1Nov11:

I got a lot further this AM. Now, instead of hard-coding for the known built-in effects it reads all known effects and builds the pref panel from that. It is now reading the prefs from CFG when it builds the page.

TODO: storing the values (I am editing the CFG file by hand right now); act on the stored values--not hard to code but a lot of new code; change the "Effects Keyboard Shortcuts" page into a TAB of the "Effects" page (I have no idea how to do that!).


Solanus 2Nov11:

If your code can read from all known effects and populate that dialog, how hard would it be to read the contents of the Plugins folder and populate the menu drop-down - including using subfolders as categories?


Edgar 2Nov11:

Not hard at all--that is my ultimate goal.

I now have the ON/OFF switch working so the user may leave effects in the plug-ins folder and turn menu items On/Off even for built-in effects. Next will be to add keyboard shortcuts and categories will come last.


Edgar 2Nov11:

After putting a lot of hours into this I think I can now see why the Developers want to await a complete make-over to the effects code before addressing these issues. I keep hitting brick walls when it comes to implementing the user's choices in re. turning menu items ON/OFF, assigning shortcuts or moving items from one place on the menu to another. I think I am going to abandon this project for now. Maybe the GUI interface in Prefs can be a starting point for a Proposal discussion.