Can a PS script (or hack) check actions On or Off?

[Signfeld]

Even "back in the day" I used to use subroutine actions — for different Fit Image settings, for example.

I would call all of those sub actions from the main action, but I'd check only the sub action that I needed for that session.

You can kinda build some workflows around that, as it saves space and you only have to maintain one version of the main action.

If a script could check these actions on or off, a PS button (action) (or other button panel out there) could then easily do that 🙂 (so yeah, you need a number of extra small actions, but in total it will still save space and time.)

I mean this checkmark here ...

 

[r-bin]

You forget about partially turned on Actions. : )

I think this can only be done by parsing the atn file.

Why does the script need Actions if it can execute them itself in any sequence?

[Signfeld]

I'm purely talking about actions here. I usually prefer actions as I like to tweak them a lot.

AFAIK, an action can not record if I check/uncheck another action, so I'm asking if this can be done by a script? (I would then connect those toggle scripts to a button)

[Stephen_A_Marsh]

Not sure if this is helpful as I'm not sure if I'm understanding correctly or not... By CMD/CTRL double-clicking an action or even a single action step, it will run just the selected action or step.

[Kukurykus]

When you assign shortcut to 'play' button like for ex. 'ctrl & f' you can also play single item.

[Signfeld]

I've assigned Play/Continue to F1. This way I can go through all Stop steps easily. So handy.

The subroutines is for the reasons mentioned above.  Just a cool option for some workflows.

Simple example...

I don't wanna create/copy 5 times the same elaborate action that may include just one step that can change (e.g., Fit Image). I want these as subactions that I can check or uncheck first. With a button (atn/script), that would be very handy.

[Kukurykus]

Maybe use conditional steps and recording actions to actions if that will help anyhow.

[Signfeld]

This is how it could look ...

I call all subactions but only preselect what I want. 

[Signfeld]

Even if you could do it, the next problem is feedback of their On/Off state.

I think something like Retouching Toolkit might be able to do that and poll the states on startup.

Before I ask them, I'm wondering if it's possible to change the state somehow...

But if you have a good memory for what you clicked, you could make a cool script too though — one that could make sure only only of the three options is selected.  But you have to be able to read and set the state of an action. Therefore my question 🙂

[Signfeld]

Well, setting them alone is already useful, no reading of state necessary.

For the three in my example, you could just turn them all off every time, then let a script "check" the one you clicked the action for. No memory needed either.  Just think of selecting what you want before the main action.

[r-bin · Accepted solution]

There is a script like act2jsx.jsx (google xtools xbytor). This is how the selected action is saved to the droplet with the subsequent parsing of this droplet to extract commands. You can also find out the status of each command there. If all are disabled, then the Action is disabled. It is a complex script and a complex method. But you can find out the state of Action.

Turning on or off these flags, at least through a script and in Photoshop until 2020 (I don't know until 2021), I think it's impossible.

[Signfeld]

Aha, I have xtools. Thank you for both tips/hints 🙂

Ok, no worries then.  I'm currently not using or needing this specifically, but if it was possible I'd build some workflows around it probably...