I suppose I could do that, but I have a whole bunch of commonly used actions grouped into one set (40+), that would be a bit confusing for anyone trying to replicate the results on another machine, etc. In this case my 'generic level' action includes a SS component that I toggle on and off when needed. I figured just copying the SS attributes as a text file along with the saved .atn file would be adequate documentation. Thanks for the different approach, I'll probably go that route for now. Still would be nice to pull out that action data though...
Maybe one could automate the saving of a new atn-file with only the selected Action to the same location as the open file with a Script – again probably not exactly easy, but if you do this often it might pay off.
There's an easy way...
Click any actions set name to highlight it, then hold down the Control + Alt keys and click open the fly-out menu then drag down to Save Actions and let up on the mouse button there. This will invoke "secret" developer functionality and allow you to save the entire panel of actions in a text interpretation.
Europe, Middle East and Africa