Moho Animation Forum

Thanks to Synthsin75 I've updated this script to access any action in the file. It is still limited to 10 key command controlled actions... BUT...

It now has a menu to choose an action without opening the action palette!

Place this file in scripts/tool folder.

http://www.lowrestv.com/anime_studio/sc ... mander.lua

Save this image to the scripts/tool folder.



Use CMD (mac) or ALT (win) + 0-9 to access the first 10 actions (it is actually 1-0, 0 is equivalent to 10)

Note: You need to save after adding new actions before they can be used by the tool. The tool reads the file format so unsaved files won't be current.


-vern

Cool, that should take the tedium out of those Shakespearean soliloquies.

This one was easy. Only took about ten minutes.

-vern

WOah , if Mike's not careful we might end up calling this Vernime.

Whoah that was quick!

MIke told me once this is exactly what he hoped people would use the scripting for. Make Anime Studio better. Create stuff he never thought of or has time to do.

-vern

heyvern wrote:Make Anime Studio better
-vern

Well you're certainly doing that.
Thanks dude

heyvern! that's absolutely cool! You should provide to the non scripter user a way to define its own set of actions names!

I can see two ways:
1) By an external txt file what defines the pairs of (action, keystroke) and the keystroke can be modified with ALT (CMD) or CTL. This external txt file should be responsability to the user to be modified. Even its length should be only limited to the user usage and the availability of shortcuts. Remember that "someone" could have been redefined those 0-9 short cuts to its own usage and would conflict with your hard coded ones. Also ten shortucuts can be so much for someone or so less for others.
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.

-G

Ah, a programmer's job is never finished... <bg>

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

Action Commander is an awesome script name.
It sounds like the name of some 80s action film, where Chuck Norris is just plain fed up, and goes around kicking people's limbs right off their bodies.

I updated the script. Read the first post.

Synthsin75 helped me with parsing the file for the action names. Works like a charm!!

-vern

Wow.
Not only is it awesome, it looks awesome.

Well done, and nice implementation

Vern, you should be able to write the hotkey number by just appending it to the action name. I'm not real sure yet how hard it will be to find the write location in the file, but if you don't get around to it, I'll let you know when I get it.


Glad I could help out with this.

This is great, Vern , thanks, we are not worthy.
Don't rest now though , you've got to stay up all night and do the next one.
You know " action array?" the idea that Selgin suggested with bones as pose sliders. C'mon now 'n' get crackin' and where's Genete , the slacker?