That command works when the item is selected in the project panel too, but it doesn't sound like what you want anyway.

Most things are achievable with scripting but often you'll have to work around the limitations and do it the best way possible with the available options.

Paul

As long as the comp is active and a single solid layer is selected you can use this: app.executeCommand(app.findMenuCommandId("Solid Settings...")); This works for accessing any/most menu items as long as the right conditions for it are met. You won't be able to do anything once that happe...

As far as I know you can't. But as Dan showed, you can use the system color picker.

Paul

I wrote the line you needed. In your code you had property(3).setValue(true) but "property" isn't a variable. You defined the variable when you wrote: var the_fx = target("Effects").addProperty("Fast Blur"); So "the_fx" is now a variable that is storing the ef...

You were so close I'm surprised you missed it:

the_fx.property(3).setValue(true);

Try this: var activeItem = app.project.activeItem; if (activeItem != null && activeItem instanceof CompItem) { var selectedProps = activeItem.selectedProperties; var y; app.beginUndoGroup("Remove Duplicate Keys"); for (var x = 0; x < selectedProps.length; x++) { if (selectedProps[x...

I don't think you'll have any luck with this. My suggestion would be to try applying the puppet to a precomp (start with a fully opaque layer so it creates a mesh across the whole frame) then make duplicate precomps and replace the still image inside it. One problem with scripts trying to create pin...

I use solos as a second activation "eye" switch too. While I also use them in the more typical way, if I get the comp into a state I like by experimenting with active layers using the solo switch, I'll leave it that way so I can still easily see which layers were active before I made this ...

As you suspected, it can't be done. The closest you can do is probably use a script to apply a smooth expression to the property.

Actually you can.

I don't think you can use both together but you could apply one, then use Animation > Keyframe Assistant > Convert Expression to Keyframes to bake the result before applying the other.

My guess would be it's the offset in pixels from the vertices to the tangent handle.

Yes we can! var activeItem = app.project.activeItem; if (activeItem != null && activeItem instanceof CompItem) { alert("renderer is " + activeItem.renderer); if (activeItem.renderer != "ADBE Picasso") { activeItem.renderer = "ADBE Picasso"; alert("renderer ...

This looks like a bug to me. I've tested it all the way back to CS3 and it's the same. When changing the inPoint, it attempts to retain the layer duration by also moving the outPoint if it can. But the new duration is off by the amount of any startTime offset (if startTime isn't zero). Subsequent at...

From what I remember this issue was pretty much laid to rest as of CS5.5. Certainly I've stopped testing for it after it previously being a problem in some of my scripts. Are you using the update() method? I think that's necessary.