P: Opacity numpad shortcut - multiple groups selected

2 Votes
LEGEND ,
Sep 08, 2013 Sep 08, 2013

Copy link to clipboard

Copied

Hi,

I've found a bug in CC when setting opacity across multiple selected groups.

Previously, selecting multiple groups and pressing numpad 5 gave all groups an opacity of 50%, whilst respecting the individual opacity setting of child elements.

Doing the same in CC results in the expected behaviour on the first group (lowest in layer stack), but also sets opacity of child elements to 50% (or whatever was entered).

Cheers!

Bug Unresolved
TOPICS
macOS , Windows

Views

72

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Apr 21, 2017 Apr 21, 2017
Thank you, Andrew!

Now I understand and see the bug.  I've gone ahead and logged a bug against it.

For what it's worth, I also have a work-around.  If the last group is not closed and you select the bottom-most layer in that group when you make the change, everything works correctly.  Agreed -- not ideal, but something to keep you outta trouble until the fix is ready.

Thanks,
David

Votes

Translate

Translate
8 Comments
Adobe Employee ,
Oct 03, 2013 Oct 03, 2013

Copy link to clipboard

Copied

Hiya Dan,

I cannot seem to reproduce this. Are you still seeing this? Could you share some more details?

Thanks,
David

Votes

Translate

Translate

Report

Report
LEGEND ,
Oct 03, 2013 Oct 03, 2013

Copy link to clipboard

Copied

Hi David,

I've made a quick video for you.

https://www.youtube.com/watch?v=BfYV_x...

Occurs when changing opacity with numpad more than once in a row. In this case, setting opacity to 50, then back to 100 - layers within are affected.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Oct 04, 2013 Oct 04, 2013

Copy link to clipboard

Copied

Howdy Dan,

I cannot reproduce this problem. There’s some step that you’re doing which I’m missing.

If you’re interested, I can set up a web-mediated Connect session so you can share your screen with me live and we can talk. Are you interested?

I'll follow up with an email.

Thanks,
David

Votes

Translate

Translate

Report

Report
Community Beginner ,
Mar 31, 2017 Mar 31, 2017

Copy link to clipboard

Copied

Hi, was this ever resolved? 3 years later i am also having this issue.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Mar 31, 2017 Mar 31, 2017

Copy link to clipboard

Copied

Howdy Andrew,

There never was a bug.  I just verified this again and it works fine for five sub-groups on both Win and Mac.

What's your setup?  What version of PS are you running?  Which OS?  What other apps do you have running at the same time?

Thanks,
David

Votes

Translate

Translate

Report

Report
Community Beginner ,
Apr 06, 2017 Apr 06, 2017

Copy link to clipboard

Copied

I'm running the most recent version of photoshop CC 2017.1

Its weird that it works fine for you, but it does the same for me on both my work and home machine...

Just to confirm what you are doing compaired to what i'm doing and the result...


> Create 5 folders, each with an item inside.
> Set each item to 60% opacity (folders still at 100%)
> minimise all folders in layers window
> Select folders and set opacity to 60%
> then bring folders back up to 100%

Result:
folders change opacity to 100%
Items change to 100% 
item in LAST folder stays at 60% opacity

Expected results:
All items stay at 60%
folders change opacity

I hope this clears this up?

Thanks,
Andrew

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Apr 21, 2017 Apr 21, 2017

Copy link to clipboard

Copied

Thank you, Andrew!

Now I understand and see the bug.  I've gone ahead and logged a bug against it.

For what it's worth, I also have a work-around.  If the last group is not closed and you select the bottom-most layer in that group when you make the change, everything works correctly.  Agreed -- not ideal, but something to keep you outta trouble until the fix is ready.

Thanks,
David

Votes

Translate

Translate

Report

Report
Community Beginner ,
Apr 24, 2017 Apr 24, 2017

Copy link to clipboard

Copied

LATEST
Thanks David, I'm glad that explanation made sense. It was hard for me to even get my head around writing it!

There are a few work arounds i have found when i just do on the fly, but its just one of those things that you don't expect to happen when your creating UX layouts with multiple changes. It doesn't happen very often mind, but when it does, some times its not noticeable as its such a small change and then you find out its gone to development and they've build in some CSS to make the last element a different transparency! 🙂

Thanks again,
Andy

Votes

Translate

Translate

Report

Report