didn't you post this question a few weeks ago? what are the keyboard shortcuts that are activating the layer move/duplication? If you tell me this much then I might have a solution. ... View more

it will help Photoshop users to know that not everything needs to rely on .jsx scripting - there are other 3rd party apps that can also monitor Photoshop as it works, and when something happens that you would like to be alerted about, it can absolutely be done. But for that to be done, it's likely that the original poster will need to pinpoint the cause of the problem. After that, it will be much easier to solve. ... View more

I think you're going to first need to determine exactly what's causing it. I'm not knowledgable enough to answer your question regarding an alert script, but if you were to determine that the layer was being moved by accidentally selecting the move tool and then dragging the layer, then I know of a few methods that could alert you every time the move tool was being selected. This alert could be achieved by showing a tooltip at your cursor, such as "MOVE TOOL SELECTED", or it could play a sound, or show a pop-up message box, or a number of other alert options. This way at least, you would know that the move tool is now active and the layer is susceptible to movement. As far as I know, there are no ways to move the layer using the spacebar or a combination of the spacebar and another key. If the layer is moving by just a pixel or two, then you're likely activating the 'nudge' command somehow. If it's moving by a large distance, then it's probably the move tool.  ... View more

how is the layer being moved? Is it being moved by accidentally switching to the 'move' tool, or is it being moved by accidentally using the 'nudge' command.. etc. If we can find out why it's moving, then there may be some workarounds... ... View more

I get a similar error sometimes. This is what happens to me and why: I create a bunch of new tool presets, and save the entire presets (.tpl file) as "ToolPresets02". Next, I select a tool preset from that new file/list via the tool preseys panel, and then open up ScriptListener, which scripted the selecting of that preset. I save the ScriptListener file as a .jsx.  Next, for example - let's say my Photoshop crashes or has been closed irregularly (through the task manager for example). Next, I reload Photoshop. When it is reloaded, because of the irregular closing a few seconds ago, Photoshop re-loads the preferences and within those preferences it loads the previous ToolPresets file (which would be "ToolPresets01") instead of loading the newest one ("ToolPresets02") - this is because when Photoshop was improperly closed, it didn't get a chance to save all the preferences.  As a result, the older .tpl file obviously doesn't include the latest tool presets that I saved. So, when I run the script (the .jsx file) to select my newest tool presets, it can't find them, because the older .tpl file is still in use. This is where it gives me the similar error (not sure of the exact number but it's in the 8000's from what I recall). I then need to replace the current .tpl file wIth the newer one in order to successfully select my new presets via the .jsx script. You might be getting an error like that due to an improper Photoshop closing.. worth checking out ... View more

yes, now it works - ensured that there were '3' empty spaces instead of "2". Don't know why that happened, but it's good now. I added one line of code at the end of the c.pfaffenbichler's script, which causes Photoshop to auto-switch to the destination document after the layer/group has been copied to it. Originally, it just stayed on the current document after copying. Having 2 versions of this script is nice, because sometimes you'll want to auto-switch to the destination document that the layer was copied to it instead of having to search through all open documents and then manually switching to it - a pain, especially if you have many documents open at once. The second version of the script (c.pfaffenbichler's original script) keeps you on the current document even after the layer/group was copied to another document, and this is useful if you're copying multiple layers/groups over to another doc - it would be a pain switching back, forth, back, forth just to copy a few layers over. thanks guys ... View more

no, it is giving me the "var idT = charIDToTypeID( "T  " );" error I use Photoshop CS6 ... View more

sorry guys, i wasn't even aware of the 'correct answer' feature - i'll keep my eyes on it from now on ... View more

one question though: is there a way to have this script work with both layers *and* groups? Right now it's only working with layers. If not, then maybe have two seperate scripts, one for layers and one for groups? ... View more

Thats it!! Awesome!!! Totally what I was looking for - this is a very useful script, i hope a lot of people see this one because they will all love it- thank you my friend!! ... View more

to further simpliy this: are there any scripts that: will open up a custom menu, and show a list of all existing documents that are currently loaded into Photoshop. This menu will allow the user to select the document they wish toi switch to, and at the same time copy that document name to the clipboard/memory? ... View more

I don't know if javascripting can do it, but you can simulate pressing the enter key with another 3rd party application called AutoHotKey - it will do exactly what you want. Check it out, it's easy to find on the web, they have their own huge message forum with thousands of sample scripts, advice, etc. http://www.autohotkey.com/ ... View more

This is happening to me as well. I will try to save an image, so I select 'save as' and I give it a new filename. Then when I hit 'save' the error message pops up. So I then repeat the process (save as, give it a new filename again, hit save again) and then it works. Happens randomly, but more often than not. The file isn't open in any other application. I can't figure it out. ... View more

Ok I see what you mean. One way to do it is to select the pen tool, then select the 'combine' option, then save this as a tool preset entitled 'Pen Combine Mode' (or whatever). Next, with the pen still selected, change 'combine' to 'subtract' and then again save it as a tool preset entitled 'Pen Subtract Mode' (or whatever you want to call it again). Now you want a way to assign these tool presets to keyboard shortcuts. Like you said, you could use actions to do this, but from what I've seen, there are a limited amount of programmable actions and once you've used them up, that's it. So because of this limitation, I've never used them since. Other than that, I don't think there's a way to assign keyboard shortcuts to tool presets within Photoshop. The solution is to: a) use the scriptlistener in Photoshop that will convert that tool preset into an executable script, and b) use 3rd party software, like AutoHotKey or PowerPro which will allow you to press any key or mouse button(or combination of both) to run that script, which will ultimately act as a keyboard shortcut. Complicated at first, but once learned, the possibilities are infinite and there are no more restrictions with keyboard shortcuts, tool presets, etc. First, look into the scriptlistener function for Photoshop, then look into AutoHotKey which provides you with unlimited keyboard shortcuts for all sorts of things. But if you can't be bothered to go that deep, then the only other way I can think of is to always leave open the tool preset panel and just select your pen presets from there once you've saved them. ... View more

I'm not very familiar with the pen tool. Is 'subtract' mode and 'combine shapes' mode something that can be programmed in Photoshop's keybopard shortcuts? ... View more

before I can offer suggestions, I need to know exactly what do the shortcut keys "-" and "=" do? I can't test this on my own as I've remapped all my keyboard shortcuts years ago... ... View more

I've tried the following codes and it works for me. It selects the parent layer of the group and then collapses it: 1. copy the following script and paste it into notepad. Save it as LayerSetSupport.jsx and save it in the same folder as all your other scripts: //START HERE------------------------------------------ //For code readability function cTID(s){return charIDToTypeID(s)} function sTID(s){return stringIDToTypeID(s)} // ============================= function openAllLayerSets( parent ){     for(var setIndex=0;setIndex<parent.layerSets.length;setIndex++){         app.activeDocument.activeLayer = parent.layerSets[setIndex].layers[0];         openAllLayerSets( parent.layerSets[setIndex]);     } }; function closeAllLayerSets(ref) {           var layers = ref.layers;           var len = layers.length;           for ( var i = 0; i < len; i ++) {                     var layer = layers;                     if (layer.typename == 'LayerSet') {closeGroup(layer); var layer = layers; closeAllLayerSets(layer);};           } } function openGroup(layerSet) {    var m_activeLayer = activeDocument.activeLayer;    var m_Layer_Dummy01 = layerSet.artLayers.add();    var m_Layer_Dummy02 = layerSet.artLayers.add();    layerSet.layers[1].name = layerSet.layers[1].name;    m_Layer_Dummy01.remove();    m_Layer_Dummy02.remove();    activeDocument.activeLayer = m_activeLayer; } function closeGroup(layerSet) {    var m_Name = layerSet.name;    var m_Opacity = layerSet.opacity;    var m_BlendMode = layerSet.blendMode;    var m_LinkedLayers = layerSet.linkedLayers;    var m_bHasMask = hasLayerMask();    if(m_bHasMask) loadSelectionOfMask();    if(layerSet.layers.length <= 1) {       addLayer();       var m_Tmp = activeDocument.activeLayer;       m_Tmp.name = "dummy - feel free to remove me";       activeDocument.activeLayer = layerSet;       ungroup();       addToSelection("dummy - feel free to remove me");       groupSelected(m_Name);    } else {       activeDocument.activeLayer = layerSet;       ungroup();       groupSelected(m_Name);    }    var m_Closed = activeDocument.activeLayer;    m_Closed.opacity = m_Opacity;    m_Closed.blendMode = m_BlendMode;    for(x in m_LinkedLayers) {       if(m_LinkedLayers .typename == "LayerSet")          activeDocument.activeLayer.link(m_LinkedLayers );    }    if(m_bHasMask) maskFromSelection();    return m_Closed; } function ungroup() {    var m_Dsc01 = new ActionDescriptor();    var m_Ref01 = new ActionReference();    m_Ref01.putEnumerated( cTID( "Lyr " ), cTID( "Ordn" ), cTID( "Trgt" ) );    m_Dsc01.putReference( cTID( "null" ), m_Ref01 );    try {       executeAction( sTID( "ungroupLayersEvent" ), m_Dsc01, DialogModes.NO );    } catch(e) {} } function addLayer() {    var m_ActiveLayer          =    activeDocument.activeLayer;    var m_NewLayer             =    activeDocument.artLayers.add();    m_NewLayer.move(m_ActiveLayer, ElementPlacement.PLACEBEFORE);    return m_NewLayer; } function hasLayerMask() {    var m_Ref01 = new ActionReference();    m_Ref01.putEnumerated( sTID( "layer" ), cTID( "Ordn" ), cTID( "Trgt" ));    var m_Dsc01= executeActionGet( m_Ref01 );    return m_Dsc01.hasKey(cTID('Usrs')); } function activateLayerMask() {    var m_Dsc01 = new ActionDescriptor();    var m_Ref01 = new ActionReference();    m_Ref01.putEnumerated( cTID( "Chnl" ), cTID( "Chnl" ), cTID( "Msk " ) );    m_Dsc01.putReference( cTID( "null" ), m_Ref01 );    try {       executeAction( cTID( "slct" ), m_Dsc01, DialogModes.NO );    } catch(e) {       var m_TmpAlpha = new TemporaryAlpha();       maskFromSelection();       activateLayerMask();       m_TmpAlpha.consume();    } } function deleteMask(makeSelection) {    if(makeSelection) {       loadSelectionOfMask();    }    var m_Dsc01 = new ActionDescriptor();    var m_Ref01 = new ActionReference();    m_Ref01.putEnumerated( cTID( "Chnl" ), cTID( "Ordn" ), cTID( "Trgt" ) );    m_Dsc01.putReference( cTID( "null" ), m_Ref01 );    try {       executeAction( cTID( "Dlt " ), m_Dsc01, DialogModes.NO );    } catch(e) {} } function selectLayerMask() {    var m_Dsc01 = new ActionDescriptor();    var m_Ref01 = new ActionReference();    m_Ref01.putEnumerated(cTID("Chnl"), cTID("Chnl"), cTID("Msk "));    m_Dsc01.putReference(cTID("null"), m_Ref01);    m_Dsc01.putBoolean(cTID("MkVs"), false );    try {       executeAction(cTID("slct"), m_Dsc01, DialogModes.NO );    } catch(e) {} } function loadSelectionOfMask() {    selectLayerMask();    var m_Dsc01 = new ActionDescriptor();    var m_Ref01 = new ActionReference();    m_Ref01.putProperty( cTID( "Chnl" ), cTID( "fsel" ) );    m_Dsc01.putReference( cTID( "null" ), m_Ref01 );    var m_Ref02 = new ActionReference();    m_Ref02.putEnumerated( cTID( "Chnl" ), cTID( "Ordn" ), cTID( "Trgt" ) );    m_Dsc01.putReference( cTID( "T   " ), m_Ref02 );    try {       executeAction( cTID( "setd" ), m_Dsc01, DialogModes.NO );    } catch(e) {} } function maskFromSelection() {    if(!hasLayerMask()) {       var m_Dsc01 = new ActionDescriptor();       m_Dsc01.putClass( cTID( "Nw  " ), cTID( "Chnl" ) );       var m_Ref01 = new ActionReference();       m_Ref01.putEnumerated( cTID( "Chnl" ), cTID( "Chnl" ), cTID( "Msk " ) );       m_Dsc01.putReference( cTID( "At  " ), m_Ref01 );       m_Dsc01.putEnumerated( cTID( "Usng" ), cTID( "UsrM" ), cTID( "RvlS" ) );       try {          executeAction( cTID( "Mk  " ), m_Dsc01, DialogModes.NO );       } catch(e) {          activeDocument.selection.selectAll();          maskFromSelection();       }    } else {       if(confirm("Delete existing mask?", true, "Warning")) {          activateLayerMask();          deleteMask();       }    } } function groupSelected(name) {    var m_Dsc01 = new ActionDescriptor();    var m_Ref01 = new ActionReference();    m_Ref01.putClass( sTID( "layerSection" ) );    m_Dsc01.putReference(  cTID( "null" ), m_Ref01 );    var m_Ref02 = new ActionReference();    m_Ref02.putEnumerated( cTID( "Lyr " ), cTID( "Ordn" ), cTID( "Trgt" ) );    m_Dsc01.putReference( cTID( "From" ), m_Ref02 );    var m_Dsc02 = new ActionDescriptor();    m_Dsc02.putString( cTID( "Nm  " ), name);    m_Dsc01.putObject( cTID( "Usng" ), sTID( "layerSection" ), m_Dsc02 );    executeAction( cTID( "Mk  " ), m_Dsc01, DialogModes.NO );    return activeDocument.activeLayer; } function addToSelection(layerName) {    var m_Dsc01 = new ActionDescriptor();    var m_Ref01 = new ActionReference();    m_Ref01.putName( cTID( "Lyr " ), layerName );    m_Dsc01.putReference( cTID( "null" ), m_Ref01 );    m_Dsc01.putEnumerated( sTID( "selectionModifier" ), sTID( "selectionModifierType" ), sTID( "addToSelection" ) );    m_Dsc01.putBoolean( cTID( "MkVs" ), false );    try {       executeAction( cTID( "slct" ), m_Dsc01, DialogModes.NO );    } catch(e) {} } function TemporaryAlpha() {    activeDocument.selection.store((this.alpha = activeDocument.channels.add()));    activeDocument.selection.deselect();    this.consume = function() {       activeDocument.selection.load(this.alpha);       this.alpha.remove();    } } // The main function //openGroup(activeDocument.activeLayer); //openAllLayerSets( app.activeDocument ); //closeGroup(activeDocument.activeLayer); //closeAllLayerSets( app.activeDocument ); //END HERE----------------------------------------------- then, copy the following code and save it into the same folder, and save it under any filename you wish: //START HERE----------------------------------------------- var doc = app.activeDocument; var theLayer = activeDocument.activeLayer; var theParent = theLayer.parent; doc.activeLayer = theParent; // ======================================================= // The main function //@include "LayerSetSupport.jsx" if (activeDocument.activeLayer.typename == 'LayerSet') {app.activeDocument.suspendHistory('closeGroup','closeGroup (activeDocument.activeLayer)');} //END HERE----------------------------------------------- now once you run the above script (the one which you gave it your own filename), it should select the parent layer and then collpase it. First make sure that the selected(active) layer is not the parent layer of the group. I beleive the main scripting here was done by csuebele, so thank him for this (sorry I don't know how to paste the above code into its own sub-window) ... View more

thanks JJ. I've read cave heiroglyphics with blindfolds on and had a better understanding of what I was reading as opposed to what you just posted, but that's due to my own lack of understanding of dpi... i appreciate the help, but I do think I finally have some sort of a grasp on this now. As I had said from the start, it makes no difference if I'm working in 72dpi or 300dpi so long as the pixel quantity is the same. The difference will be the document size (in inches), and that can be re-sized when going to print - so yes, I have learned something new today.  So in essence, dpi is something I should eliminate from my vocabularly entirely, and replace the word with 'pixels' - so long as I keep an eye on the document size first (inches) and then convert if necessary. Hopefully I get it now. thanks also for all the additonal help here. ... View more

it's traditional artwork, as I have already stated Trevor - see above, I have mentioned that one of the projects is a portrait with a pastel-look. I'm only developing and delivering the artwork, and am working under requested guidelines of 300dpi. The client will take care of the printing. So they ask for 300dpi, I give them 300dpi, it's my job. But it seems that this could have been done at 72dpi as long as the pixel quantities are the same, but I think I'm cluing in to the fact that if it's done at 72dpi then it will be a much larger print, which would be intended to be viewed at from somewhat of a distance ( a large poster maybe). Changing it to 300dpi would shrink it down in physical size, meant to be viewed from a closer distance when printed (a picture book maybe). Starting to make sense now. So whether I work in 72dpi or 300dpi doesn't matter - this much has been explained well and now I think I understand (I hope).. by the way I love the exploding head Trev , lol ... View more

because Photoshop and Illustrator are two different programs. They work with graphics differently. Photoshop works with rasterized images, and Illustrator works with vector images. This is why the line in Illustrator never becomes blocky even when you keep zooming in. If you need sharp vector lines then stick to Illustrator., Photoshop isn't going to do what you need because it wasn't designed for that. Just like Microsoft Word wasn't designed to mix audio tracks, Photoshop wasn't designed to work with vectors (which is what you are looking for.) You need to stick with Illustrator or something similar ... View more

sorry, this is all just a blur now. It's not just me - do a simple search over the internet for this issue and you'll find that there are several theories on this... hence the mass confusion and mis-undertanding of this entire subject all around the globe..so before you shoot me, please understand that i'm not the only one having a hard time grasping this all I know from my position is that so long as the pixel count is the same, it doesn't matter what dpi the document is at. 72dpi 4800x6000 pixels will yeild the same image editing quality as 300dpi 4800x6000 pixels. As long as the pixel quantity is the same, it doesn't matter what dpi it's at. This is what I am now beginning to understand.   But working at the 72dpi 4800x6000 level means that the physical document size goes way up from 16 inches x 20 inches to 66.667 inches X 83.333 inches. Does this mean that when the image is printed, it can print at that enormous size with no indication of quality loss of the print? If so, why does the 300dpi image print only at 16 inches x 20 inches? Can you bump it up to 66.667" x 83.333" with no quality loss? i'm sorry but this has spiralled way out of control, i just do not get it.. i really wish i was one-on-one in person with someone to figure this out, we could sketch it out and again trevor, i've specified that this is only for traditional-type artowrk, for work such as pastel drawings, watercolors, etc. there is no photography involved. I'm never sure of the paper used to print on, because that is up to the publisher that i submit the work to. they only specify that the work be deliverd at 300dpi, 16 inches X 20 inches. So my question is, why can't I deliver it to them at 72dpi, 16 inches X 20 inches if it makes no difference? ... View more

i'd like to add something here - after researching this a bit more, I've discovered a setting which has yet to be mentioned: the setting is "resample image" and is found in the window when you re-size the document. I have had this option checked on all this time (it's the default).  So this meant that every time I went from 300dpi to 72dpi, it also reduced the amount of pixels... which totally reduced the quality of my image in terms of being able to edit it/zoom in closely to it to paint details. If I deselct 'resample image' before sizing down to 72 dpi, then nothing about the image quality changes - becausr the amount of pixels now stays the same - hence this is the problem I've been dealing with all this time. I didn't realize that I could keep the quantity of pixels the same by simply un-checking this option.  I knew this was something simple, but I couldn't figure it out. You must de-select 'resample image' when reducing the dpi in your document to maintain the same clarity when continuing to edit your image. Took a while for me to find this information, though... the only last stumbling block is to now understand that if you reduce down to 72dpi and keep 'resample image' deselected, then the image quality remains the same but the document size increases from something like 16"x20" way up to 66"x83"... does this now mean that when you print it, it's going to print out at that enormous size (66"x83")? ... View more

it's starting from scratch. All drawing and painting with chalk, watercolor and pastel brushes. Trying to emulate a real traditional, canvas-type look. A pastel portait, for example. There's no photograph. Just a blank photoshop document to start it off. Same image/painting, with these characteristics: a)  16"x20", 300dpi = 4800pixels x6000pixels... excellent image quality when drawing/painting in photoshop at print size, and also when zooming in - I can zoom in very closely (way closer than print size) before anything becomes "pixellated" or "blocky" then, after dropping the same image down to 72dpi (just drop the dpi to 72, do not change pixel pr physical dimensions): b)  it now becomes 16"x20", 72dpi = 1152pixels x 1440pixels... good image quality when viewed at print size (but not as good), and horrible image quality when zooming in even one level above print size. ..what am I missing here. For the 72dpi one to look as good as the 300dpi, do I need to first drop it to 72dpi, and then increase the pixel dimensions *back up* to 4800x6000 to achieve the same clarity? If so, then the physical dimensions of the image increase way up to 66.667" x 83.333" - does this mean that the image will print out at this size? If so, then obviously I would redeuce the physical size back down to 16"x20" and voila - it's like I'm going in circles. I'm as frustrated as anyone else in this topic, but moreso for me because I'm just not seeing where the difference lies, and I'm clearly missing something that's probably so simple. ... View more

i DO intend to print - which is why i'm trying to figure this all out. i need to print out at 16x20. so whether it's option A or B makes no difference. For option B (72dpi, before printing it, I would need to first flatten the image and then reduce its physical size from 66"x83" down to 16"x20" first). forgive me for all the extensive questions - but all along i've been obsessed with using a 300dpi because i've always thought this is automatically a better printout result. Which seems to not be the case after all this time ... View more

appreciate the help. bottom line, it seems that my scenario (image A vs. image B) are the same - so it doesn't matter which one I work in. I just don't know why the option is there in the first place to change the resolution/pixels if both scenarios perform the same and look the same when printed out. ... View more

thanks, I'm learning something here. Let's say I have two *identical* documents open in Photoshop: Image A:   16"x20", 300dpi, = 4800x6000 pixels Image B:   66.667"x83.333", 72dpi, = 4800x6000 pixels (Image A and B are the same picture, only at different resolutions and print sizes) ...are these two images esentially the same? And you're right, I do not notice a difference in photoshop performance betweeen these two images. The brushes work at the same speed on both. But my question - what's the difference? If both look the same when printed out on the same type of paper, same printer, etc, and both have the same photoshop performance when drawing/sketching with them, then why would I use A instead of B (or vice-versa?) ... View more

ok let's say this - I'm using photoshop to do cartoon artwork for children's picture books. No photography is involved, just sketching/painting and using all kinds of brushes with photoshop. The artwork will be printed out into books that people will purchase in bookstores. Is 300dpi for this a waste of time? Should I be using 72dpi instead (because it's faster?) If so, why are publishers insisting on 300dpi for the prepared artwork? for example, each page is 12x14. the requested image resolution must be at 300dpi. this equals 3600x4200 pixels (but they don't mention this, the only specify that the artwoprk *must* be prepared at 12"x14" 300dpi). if i drop it down to 72dpi, then the pixels become 864x1008. what's the difference then? is there a difference in quality when it's printed out? If not, why are the publishers asking for 300dpi ... View more

the question is: 1. what are the advantages of using 300dpi as opposed to 72dpi? 2. why would we use 300dpi instead of 72dpi? is it for printing purposes only, where 300dpi would result in a more sharp, crisp printout? ... View more