Simple example of code and Console output while looping through two layers: [image]

Any update maybe? Now there’s no way to actually correctly avoid this issue when multiple layers are active, but you want to rename just one. Same goes for color change via BatchPlay

Hello, I haven’t noticed the fact that renaming a layer with UXP code or changing a layer color with batchPlay has an impact on layer visibility. Parsing the PS layer stack is very useful. Have a look here https://www.adobe.io/photoshop/uxp/guides/ps_basics#layer and here https://www.adobe.io/phot…

I really appreciate your thorough response, but I didn’t find anything useful to me for solving the problem. All your notes are exactly what I do on my plugin, but that just doesn’t work. Also this [image] Pierre_G: To access the current layer, I’d use: var currentDocument = app.activeDocumen…

[image] Pierre_G: var currentDocument = app.activeDocument var layers = currentDocument.activeLayers; var currentLayer = layers[0]; Indeed, in the case of multiple selected layers, you’d get the lower “z-index” PS stack layer. If you parse the layer object and check recursively for its props…

OK I think I managed to make my plugin work, but quite a huge part of script is just workarounds for visible/active issue… My plugin heavily relies on layers activity and a bit on visibility, so almost every single action is wrapped into something like this: Set needed layers active/visible states …

It appears renaming a groupLayer or setting a color also expands it. What’s the deal with setting layer one or another property, messing up a bunch of other properties?

Neither renaming via batchPlay, nor renaming via the DOM classes expands the group for me: [image] Also, group expansion in the layer panel is no scriptable property after all, so you can’t programmatically change it. Maybe something in your code is causing the Interface to expand it as a side eff…

[image] simonhenke: Maybe something in your code is causing the Interface to expand it as a side effect. Maybe. I’m already pulling my hair out. It should be so simple, but I’m slowly getting furious… At least there was a way to add breakpoints and debug normally. Or is there?

You can debug & set breakpoints in the DevTools, can’t you? I just never use it because I don’t know how well it harmonizes with bundlers like webpack etc. Console.log all the way :smile:

[Bug] Changing layer name, changes layer to visible

Photoshop UXP Plugin API

Karmalakas December 9, 2020, 11:01pm 2

Setting layer color using batchPlay(), also makes layer visible

[Bug] Can't rename inactive layer

Topic		Replies	Views
[Bug] Can't rename inactive layer UXP Plugin API bug , uxp , javascript	21	943	February 20, 2021
(Again) Create Layer on top of every other layer through pure batchPlay UXP Plugin API	48	1892	November 11, 2022
Cannot enable/disable layers. Nudging layer moves selected layer not layer variable UXP Plugin API javascript	8	432	April 15, 2021
Select group by layer name problem Photoshop uxp , javascript	1	60	March 13, 2025
Move Layer to Front through batch-play works differently in PS 23.4.1 UXP Plugin API batch-play	46	2339	July 10, 2022

[Bug] Changing layer name, changes layer to visible

Related topics