Run scripts, menu commands and apply expressions, from a searchable list or custom toolbars. Open script interfaces from anywhere in pre-docked panels.
Gah bit of a let down - many scripts don't seem to have the "Show UI in tl_panel" option.,..?
The scripts in the "ScriptUI Panels" folder are added by default as menu commands that opens up the scripts panel (same as opening them from the window menu).
If you would like to open them in the tl_panel, you can add the "ScriptUI Panels" folder to Tool Launcher (In the paths tab) or add a new tool that points to a script file, for each of the scripts you want to open in tl_panel.
So nice!! Finally the missing link in script management, as ft-toolbar kind of stopped evolving. Hope You will keep this alive and improve still a bit!
What would still be greater:
- Of course some more documentation (eg. how to integrate Menu commands or how to have multiple tl-bars)
- Color buttons/labels (or color text)!
- Some simple formatting options within tl-bar
- Some simple Script/Expression collections or Sample Packs
(and i experienced some formatting conflicts in the contents box, mainly with quotation marks)
Hello man, how can i manage "menu" command? Creating New Solid button for example?
In the settings window you can create a new tool and set its type to "menu", then in the text box below you write the name of the menu command you want to execute, exactly as it appears in the menu. e.g "Solid..." for creating a new solid.
Hello man, how can i manage "menu" command? Creating New Solid button for example?
In the settings window you can create a new tool and set its type to "menu", then in the text box below you write the name of the menu command you want to execute, exactly as it appears in the menu. e.g "Solid..." for creating a new solid.
Hello man, how can i manage "menu" command? Creating New Solid button for example?
In the settings window you can create a new tool and set its type to "menu", then in the text box below you write the name of the menu command you want to execute, exactly as it appears in the menu. e.g "Solid..." for creating a new solid.
So, it's like: Layer New "Solid", or not?
You only need to write the text of the item you press in the menu, the last one, not all the ones you press to get to it. And it needs match exactly, so for a solid it is "Solid...", with the three dots, just writing "Solid" won't work.
Hello man, how can i manage "menu" command? Creating New Solid button for example?
In the settings window you can create a new tool and set its type to "menu", then in the text box below you write the name of the menu command you want to execute, exactly as it appears in the menu. e.g "Solid..." for creating a new solid.
So, it's like: Layer New "Solid", or not?
You only need to write the text of the item you press in the menu, the last one, not all the ones you press to get to it. And it needs match exactly, so for a solid it is "Solid...", with the three dots, just writing "Solid" won't work.
Man, i'm new in expression, i just want one simple button for new solid. How should i write it exactly? Solid... creates solid not inside a comp
I love the launcher! Would be really nice to be able to turn off the outline of the buttons so you just see the custom icons. Also it would be really cool if you could save a tool that doesn't have the ability to edit it.
Also it would be really cool if you could save a tool that doesn't have the ability to edit it.
I'm not sure how this would be implemented. Would you be so kind to open a support ticket detailing how you would use this, and how you think it should work?
There is a way to hide the "Command" field in the settings for individual tools. In the config file you can add '"cmd": { "hide": true }' to the tool you want to hide.
(tool launcher or ft_toolbar) both of them cause a meesage Error
(( error writting some icons file ))
every time i start up aftereffects .
This might be a permission issue or one of the icons have been corrupted. In the next update you will get a list of icons that causes the error to appear.
Would be possible to add scrollbars to the 'tl_bar" and 'tl_panel' the same style like 'tl_list'.
It's on the todo list to add it to tl_bar. It's just not that straightforward to add. I have currently no plan to add it to tl_panel as that may interfere with other developers UIs and cause problems.
Is there a user guide to this script? All I see are a list of features. I find it behaving in unexpected ways. My script panels are opening up in their own undocked, floating windows instead of the tl_panel. I'm not sure how to troubleshoot this.
Is there a user guide to this script? All I see are a list of features. I find it behaving in unexpected ways. My script panels are opening up in their own undocked, floating windows instead of the tl_panel. I'm not sure how to troubleshoot this.
There should be a pdf in the zip file you downloaded with the product.
You have to have tl_panel opened from the window menu, and the script you are trying to run must be able to be docked (i.e the script author intended the script to be opened from the Window menu).
Is there a user guide to this script? All I see are a list of features. I find it behaving in unexpected ways. My script panels are opening up in their own undocked, floating windows instead of the tl_panel. I'm not sure how to troubleshoot this.
There should be a pdf in the zip file you downloaded with the product.
You have to have tl_panel opened from the window menu, and the script you are trying to run must be able to be docked (i.e the script author intended the script to be opened from the Window menu).
Thank you for your response, I unzipped to a cluttered Downloads folder and missed the documentation. I see it now.
Regarding the docking, all the scripts I'm using are accessible through the Window menu and I do have the tl_panel window open it won't populate. I'll run through the documentation and see if I can fix it.
I'm sorry to say this but the entire PDF help file is ridiculous painful to follow. Words are used incorrectly. Hence, what is a simple routine becomes a huge maze of absolute mind fuckery. Can you please get someone to look at the documentation? There seems to be little relationship between what is written and the UI. You need to add some screen caps at the very least. Thank you.
Suggestion for Version two - it would be great to have the ability to add keywords to each script and then be able to search by those key words. Sometimes scripts names are vague and it's hard to know what it does by it's name only. I have over 200 scripts and this would solve a lot of issues.
Hi! Is there a way to create a keyboard shortcut to open tool launchers tl_list ? I tried to place it in the script folder to access it via the "ExecuteScriptMenuItem" shortcut command line but that doesn't work as the tool launcher script only works in the ScriptUI panel Folder. Any idea?
Is here the best place to give feedback/requests?
The scripts in the "ScriptUI Panels" folder are added by default as menu commands that opens up the scripts panel (same as opening them from the window menu).
Thanks dude. Pinging you some future requests :-)
Is there a way to save my current state of configurations to a file?
I ask because I make changes and then I have to keep remaking the same changes...
I see the Path tab with the path to the config file but it is unclear what that does.
There should be, I think, a clear button to save the current state...
But is it possible to add normal effects from AE in "tl_bar"?
I tried ur config file and it works just fine .
You have to have tl_panel opened from the window menu, and the script you are trying to run must be able to be docked (i.e the script author intended the script to be opened from the Window menu).
Regarding the docking, all the scripts I'm using are accessible through the Window menu and I do have the tl_panel window open it won't populate. I'll run through the documentation and see if I can fix it.
Can you open a support ticket on that issue? It's easier to help you that way.
Thanks!
This will be fantastic!
And yes, even thought it's fairly intuitive, a tutorial will be great