Layer Merge Behavior

When I merge two or more layers in photoshop the name of the first layer selected is the one that is preserved. Same thing with Illustrator's swatches. If multiple swatches are merged the first name selected is preserved. However, when multiple layers are selected in illustrator the name that is preserved is the last one. Why this inconsistancy in behavior?

Thanks for the explanation Larry, but I don't understand what the resulting name of a layer has to do with the Z-order of the objects in those layers? If I select the top most layer last, the resulting merged layer will have it's name; and if I select the bottom most layer last, the resulting layer will have that name. All the objects will still have the same stacking order regardless of which way I merge. I just want the naming convention to be the same as it is in other adobe programs, and within illustrator itself for all other merges.

Similar Messages

Photoshop CC: Layer Merging Behavior with Timeline Animations (Bug?)

Hello,
we're working a lot with the Photoshop timeline in our company. After upgrading to Photoshop CC we encountered a behavior that was different with CS6.
Picture a file with a timeline animation consisting for example of 8 frames, with 8 layers, each layer's visibility exposed on a single frame (layer 1 exposed in frame 1, layer 2 exposed in frame 2 etc) and all other layer not visible.
In Photoshop CS6, if I were to create a new layer for example in frame 4 of my timeline above layer 4 (which is the only visible layer in this frame) and merged it back down onto layer 4 (by selecting it and pressing the shortcut CTRL+E), the resulting layer inherited all the exposure settings of layer 4, but did contain the merged visual content of layer 4 and the previously new layer above it. This is what I want.
Now in Photoshop CC, when doing the very same action, the layers are merged and keep the naming of layer 4, however the visibility flag is not inherited properly. The resulting layer is exposed (visible) on all frames in the timeline, whereas it actually should only be exposed in frame 4.
Also note that the timeline option "New layers visible in all frames" is deactivated. So even if Photoshop treated the merged layer as an actual new layer, it shouldn't expose it's visibility in all other frames.
The only workaround I've found so far is enabling "unify layer visibility", hiding the layer, then disabling "unify layer visibility" again. This is annoying however, and the entire new behavior seems like a bug to me. Can any of the developers comment on this? Thank you.
Regards,
Hannes Drexl

My only solution so far is to avoid using CC and sticking with CS6. Thanks Adobe for not letting me enjoy the other great features of the PS version you seem to care about updating and improving. Since PS is the main reason I even subscribed to creative cloud, it would be nice to at least know this problem is being resolved in the future.

Colour changed after layer merge or layer flatten

Hi All,
After making several adjustment layers, the layer merge is performed. However, it is observed that the colour changed after layer merging. It is confirmed with the histogram. This phenomenon also happens in layer flatten. Any solution?

Not sure if this is related, but a previous post had color shift when he converted from RGB to any other profile and then back to RGB. Figured it was a rendering problem. Although he had latest video drivers he went back to previous one and solved the problem.
By any chance did this start after a driver upgrade?

Adobe Ideas Layer Merge

First, thanks for the update. With this new update you've brought many features I was hoping for and an already awesome app has become near perfect... Except for a few things. One of the biggest things I'm seeing that will need to be corrected is that when you merge layers you can't undo after confirming the merge. Today I did a sketch in Adobe Ideas with the pencil tool, lowered the opacity and started "inking" on layers above it. Everything was going great until I accidently merged my "inks" layers with the sketch layer bellow and, sadly, was unable to Undo the merge.
Hopefully, while this isn't a bug, this can be addressed in a future update.
Again, thanks for an amazing app that gives my iPad even more value.

Hi Eric_Merced,
Thank you for the feedback. I'll report the behavior to our developers to see if its something which can be changed in the future.
-Dave

I don't get a fluent blending( the transparant 'checkboard layer' merge with the images instead) of the images i like to blend

I like to fluently blend in more images , When i use the gradient tool and hold down the shift key to draw a line , i see no fluent transition of the two images, instead part of image fades into a tranpanrant ' check board' layer instead.
What goes wrong here?
Blending Multiple Images in Photoshop | IceflowStudios - YouTube
I am refering to the tutorial above..

Yes, I understand it's not always easy to grasp to what goes on on the other side.
I already tried the above though nothing seemed to work
I had to use the paint brush as well but in reverse setting to get the desired result. If I dont use paint brush the checkboard appears thus it wont merg/ blend the images.
I don't understand how the guy in the video did this but with photoshop cc 2014 it seems to work different, apparantly.

Retaining layer styles in a text layer merge down

I created some text and added layer styles to it. However when I merge the text, first rasterizing then merge down, I lose the layer styles. The text goes to its original color and no shadow, no stroke, bevels or anything else.
on a Mac CS 5.5 OS 10.6.8
Thanks in advance

Hi,
If you view the image at 100% view (actual pixels) before rasterizing and merging, does that make a difference?

OutOfMemory from UnitOfWork and strange Merge behavior.

My object model is like this:
Object A has a list of object B(One-to-many mapping, readOnly for this attributes).
Each object B back refers to A(bi-directional, one-to-one mapping).
My application has only one DatabaseSession.
In one thread, I need to go through a loop for about 200 to 500 times.
The code is like this
int n=200;
for (int i=0; i<n; i++)
     UnitOfWork uow=session.acquireUnitOfWork();
     A aclone=(A)uow.registerExistingObject(a);
     B b=....;
     aclone.addB(b); // b's A will set to a inside of this method.
     long startTime=System.currentTimeMillis();
     uow.commit();
     long endTime=System.currentTimeMillis();
     System.out.println(String.valueOf(endTime-startTime));
If n is less than 100, the topLink behaves consistently.
It takes less than 100 milliseconds to add an object B into database.
However if the n is 200 or bigger, the time for each UnitOfWork.commit() is sharply
increased(from 1000 to 8000 milliseconds). Finally it throwed an OutOfMemory exception.
I have a DescriptorEventListener registered for my class. This DescriptorEventListener monitors
the postMerge event. I expected that in each loop, the merge of the clone to
original object should be called for the one new object I inserted. It is indeed called
for the object b. However The merge is called for all existing bs
associated with A. Maybe it is why it takes more and more times to add a new B to A atomically.
Anyone has the same experience or any suggestion to solve this problem.

When I added the Nth b to A, A only has (n-1) b associated to it (the bs I added in the loop).
I tried your suggestion. It did not work.
I got this exception.
EXCEPTION [TOPLINK-6004] (TopLink - 9.0.3 (Build 423)): oracle.toplink.exceptions.QueryException
EXCEPTION DESCRIPTION: The object [com.test.A@7c4c51], of class [class com.test.A], with identity hashcode (System.identityHashCode()) [8,146,001],
is not from this UnitOfWork object space, but the parent session's. The object was never registered in this UnitOfWork,
but read from the parent session and related to an object registered in the UnitOfWork. Ensure that you are correctly
registering your objects. If you are still having problems, you can use the UnitOfWork.validateObjectSpace() method to
help debug where the error occurred. For more information, see the manual or FAQ.
QUERY: WriteObjectQuery(com.test.Parent1@7c4c51)
     at oracle.toplink.exceptions.QueryException.backupCloneIsOriginalFromParent(Unknown Source)
     at oracle.toplink.publicinterface.UnitOfWork.getBackupClone(Unknown Source)
     at oracle.toplink.publicinterface.UnitOfWork.getBackupCloneForCommit(Unknown Source)
     at oracle.toplink.queryframework.ObjectLevelModifyQuery.prepareForExecution(Unknown Source)
     at oracle.toplink.queryframework.WriteObjectQuery.prepareForExecution(Unknown Source)
     at oracle.toplink.queryframework.DatabaseQuery.execute(Unknown Source)
     at oracle.toplink.publicinterface.Session.internalExecuteQuery(Unknown Source)
     at oracle.toplink.publicinterface.UnitOfWork.internalExecuteQuery(Unknown Source)
     at oracle.toplink.publicinterface.Session.executeQuery(Unknown Source)
     at oracle.toplink.publicinterface.Session.executeQuery(Unknown Source)
     at oracle.toplink.internal.sessions.CommitManager.commitAllObjects(Unknown Source)
     at oracle.toplink.publicinterface.Session.writeAllObjects(Unknown Source)
     at oracle.toplink.publicinterface.UnitOfWork.commitToDatabase(Unknown Source)
     at oracle.toplink.publicinterface.UnitOfWork.commitRootUnitOfWork(Unknown Source)
     at oracle.toplink.publicinterface.UnitOfWork.commit(Unknown Source)
     at TestAdd.main(TestAdd.java:58)
That means that I have to register the object A. This is really bad feature for UnitOfWork. I just want to add a new Object B. Why does I need the burden from A?
This brings up another question. If I do not want the burden from A, I need to break the association from A and B and maintains the relationship manually. However I really wish my persistence layer can handle the association transparently for me.
I also notice that you suggest all the 200 bs in a UnitOfWork. In my situation, I need 200 UnitOfWork, I need to add each b in a separate UnitOfWork. When I call the UnitOfWork.commit(), the UnitOfWork is released cleanly. Is it right?
Thansk

Layer Palette Behavior When Opening AI Docs

Whenever I open a multi-layered AI file, all of the layers and sublayers are automatically unzipped (i.e., the disclosure triangles are all downturned by default to expose every layer -- ugh).
Upon opening an AI document, I would like for the layer disclosure state to match the layer disclosure state of the document at the time the document was last saved and closed.
Is there a way to change the default behavior of Illustrator here?
Thanks,
Mark Oehlschlager

Nope, It's been this way for multiple versions now. It somehow relates to having Groups of Groups. I have a couple of maps that do this and I have to change it every time I open them.

File corrupted.... all layer merged in one! it's all black!!!

Hi to everybody
i need an help!!!
While i was working on Photosop, the pc is gone freeze... and i had to reset it holding power button!
After the restart my file was completely black! The size is 188Mb .... but all layer are merged in one...black!
In photoshop browser i can see the preview of the file....but when i open it... ... ..nothing!!!
Can someone help me? pleaseeeeee!!!!

Exactly what were you doing when your PC froze? Were you in the process of saving your file?
You should check your Windows logs ASAP on the chance that your computer itself is failing, before trying to do any more work with it!
I'm sorry to say that based on what you've written, chances are your Photoshop work on that project is gone for good. There is usually no recovery.
This is why people do File - Save fairly often, and into multiple different files during long projects, when running Photoshop.
However, you *may* be able to get back a flattened version, depending on how you have the compatibility option set for saving your PSDs, by using a program like IrfanView to open the flattened composite in the PSD file. It's worth a try.
-Noel

Folder merge behavior

I am a new Mac user (why did it take me so long?!). I am bringing data together from two different PCs with similar folder structures and have been struggling to understand Mountain Lion's folder merge functionality. Research on the web has not revealed much other than this functionality is new and I cannot find any detailed documentation that would help.
My question is this: when I merge two folders with the same name, both with multiple sub-folders, many of which also have the same names in the same places in the hierarchy and where there will be a mixture of new files, duplicates and different versions of the same files, what is the behavior of the merge function (command and drag)? Specifically, how are subfolders treated? Are they merged as Windows merges them, with options to "keep both" or overwrite with the newer version in the case of duplicates and combination of distinct files right down the hierarchy?
I am nervous because I read somewhere that Mountain Lion merges the top level folder is this way, but replaces all subfolders per previous Mac OS behavior.
Thanks in advance.

The Finders functionality for folder merging is very limited.
It wil work if the folder being copied has no sub-folders.
If you wish to copy an entire folder structure from one place to another, you can use a Terminal command:
ditto -V sourcefolder destinationfolder
This will copy sourcefolder into destinationfolder, retaining the unique files of destinationfolder, but over-writing any files that have the same name as the one in sourcefolder.
Alternatively, you can use the a different command to prompt you as to whether or not you want to over-wrote files that have the same name:
cp -R -v -i sourcefolder/. destinationfolder

"Photoshop classroom in a book" chapter 12 wine glass disappears after 3D layer merging. the object didnt disappear it is just smaller, it is labeled objmesh is the 3D panel.

you can select the objmesh layer in the 3D panel and scale the image up to see the wine glass. It took me a wfhile to think of this because the book does not tell you to rename the wine glass file when you import it. So if you are looking or the words Wine, or Glass, or both you will not find them. Once again the Wine Glass layer is labled "objmesh"

the book i have does not state which edition it is. But as you can see, i found the file, it was just mislabeled. i osted this just in case someone else has the same problem.
Steve

Z-rotation of a 3D element parented to a moving NULL layer: WEIRD behavior

Hi all,
Never encountered this before!
I have a bunch of little 3D elements parented to a null layer that moves along the X axis (for consistent horizontal movement of all elements).
Separate X and Y rotations on the individual elements works great, but as soon as I try Z rotation, I get really strange "planar" rotations. When I un-parent a 3D element, the Z rotation works great...only now it's no longer parented!
What's up with THAT? You can perform X and Y rotation on a 3D element parented to something else, but not Z rotation?? I don't understand this at all.
Anyone have any insights into this?

Thanks Aaron.
I don't know if the fact that the NULL object was scaled had anything to do with this, but I ended up relegating each 3D object to its own composition, and then parented those to the NULL object, which worked.
Probably the long way around, but next time I'll know to look for any scaling issue before I start :|

Strange Layer Style Behavior CS3

I'm having a problem with creating a custom layer style. When I click the layer style button at the bottom of the layer pallet, or chiise a layer style from the Layers menu) Photoshop does not open the Layer Styles dialog box. It instead applys some sort of default style and I see a message in the top tool bar that says "Click and drag to reposition the effect." Double-clicking the layer in the Layers Pallet switches to the hand tool and disables most menu functions. I either have to hit Enter or Cmd-Period to cancel and return to normal functionality.
Is this some arcaine setting I've never encountered before, or is PS broken? The problem seems to have started after I ran the OS X Software Update yesterday-- I'm using OS X 10.4.11. I also recently switched my Workplace setting from a custom two-monitor pallet layout to a single monitor default layout.
Thanks--

It seems like the layer effects dialog is popping up off-screen somewhere... When you double-click on a layer with styles/effects applied to it, it usually pops that up, and then if you mouse over the image while that's up, you get the hand tool and allows you to drag to reposition the effect.
That would also explain the disabling of the menu items, that also happens when the layer styles dialog box pops up.
I'm not sure how you go about fixing that, though... I would try saving your workspace layout as something else, and then hitting window>workspace>"reset palette locations" or "reset menus" (although you'll probably lose any custom menu stuff that way) and I would also try applying other default workspaces.
Best of luck!
-Caleb

Layer.translate behavior in configurator panel

i have a simple panel with a Script File button to execute the following script:
app.activeDocument.activeLayer.translate(256);
When i click this, I get:
The object "previous history state" is not available
This was part of a larger script that has some funky bahvior when running through configurator. Through ESTK, it works as expected. So I narrowed it down to this.
Why is it trying to do history state stuff?

May be here your solution :-)
http://www.ps-scripts.com/bb/viewtopic.php?f=2&t=4041

A bug? Layer styles change or dissappear when you flatten/merge layers.

Does anyone else experience this problem in CS3?
An example for me would be,
right now I have an outer glow with noise applied to something but when I flatten the few layers I have in the file, the noise simply disappears or the glow becomes faded. With other layer styles, there might be a change, too, but usually the effect just weakens in color when i flatten the layers.
any advice would be much appreciated, thanks.

I either used too many words or too few, but I'm not really sure.
The specific layer style combo and layer merge I am talking about is simpler than you might imagine..(see the pictures I posted of the results of the merge.)
Yellow outer glow at full opacity with 100% noise, merged down with a single layer. (and that single layer does not have anything other than a fill in it)
When i merge the two, (both blending modes are set to normal) the noise then disappears and the glow fades. It really does not have anything to do with how close or far away the "view" is.
Trust me, I tried it.
I even used a microscope and a telescope..
It doesn't change anything.
In other words, the layer styles always look okay regardless of how they are viewed, UNTIL you flatten or merge them.
So to finally answer Buko's question, the answer is no.
And I did actually take into consideration what D.Katz said about possible interference with the appearance.. view needing to be at 100 to even judge what's going on.
The problem I am experiencing only occurs the minute one layer combines with another layer that has a layer style(s).
If you compare the two images I posted, you will see that there is a very large loss in quality rendering the layer style not even worth using in the first place.

Layer Merge Behavior

Similar Messages

Maybe you are looking for