Genete wrote:heyvern! that's absolutely cool! You should provide to the non scripter user a way to define its own set of actions names!
2) By other script that reads the keystrokes to assign the action. You can do it by calling button script that read the current action in edition and ask to the user for a keystroke modified or just write it is a predefined format. It would be a little more difficult to create but finally easier for newbie users. Also you can start with the first option and create this second option later based on that external file.
Hmm.... I was planning to use the first idea, but I really like this second one.
So, while you have an action "active" you click a button and type in a key for the shortcut. I could put in a list of "reserved keys" to prevent people setting a bad key command.
This button would write a new file or edit an existing file to create the key command list.
The big problem I have with using a script to write these stupid files is that after a while they pile up and it's hard to keep track. I am using my bone groups script for a long time now. It writes files to store the groups, one for each file. So now in all my project folders I have all these "extra" files cluttering things up. It's useful but messy. Now I would have yet ANOTHER file unless I incorporate it into the bone groups file I'm using.
It would be so FANTASTIC to be able to store this TINY SIMPLE info IN THE FILE FORMAT. Dagnabbit... all Mike has to do is change AS so it isn't so picky about attributes in the file format that AS doesn't understand. Just read to the end of the file and anything after that is user defined.
I have yet to find a spot in the file to store this data. An empty layer might work but it's too risky the user would delete it. A notes layer maybe... <sigh>
Hey! For this script only... I could create a "blank" dummy action. This action's name could hold the other actions names and key shortcuts using a long string sepearted by hyphens or underscores, something easy to break it up and get the info from.
The user would have to make sure they never delete or use that action.
This might work.
p.s. I finally have a "cool" name for one of my scripts.
Action Commander. I love it.

-vern