Hi Guys,

To my knowledge, this is the first time this issue with modeless windows has been raised. I know I haven't seen it (but can't recall specifically if I've ever made a modeless window in Ps). Could you send an example that manifests the bug?

There is a known bug in PS that prevents using the CSAW lib downstream of a system event. That bug manifests with the same error, and sometimes a Ps crash.

It's possible you're seeing something related caused by the modeless context. You could try using the workaround posted here: http://cookbooks.adobe.com/post_Creative_Suite_Extensions_and_the_Phot oshop_CS5_Re-17727.html

If I can get an example, I'll have a look at it today.

Regards

Bob

When I look at the script listener output, I see something way different from what you have in your code.

What I see is in the dupeLayer function (shown below).

If I replace your code with something like this:

function run()

{

          alert("We have a JS link");

          #target photoshop

          dupeLayer()

//           var idCpTL = app.charIDToTypeID( "CpTL" );

//     executeAction( idCpTL, undefined, DialogModes.NO );

}

function dupeLayer() {

          var idDplc = charIDToTypeID( "Dplc" );

                    var desc7 = new ActionDescriptor();

                    var idnull = charIDToTypeID( "null" );

                              var ref5 = new ActionReference();

                              var idLyr = charIDToTypeID( "Lyr " );

                              var idOrdn = charIDToTypeID( "Ordn" );

                              var idTrgt = charIDToTypeID( "Trgt" );

                              ref5.putEnumerated( idLyr, idOrdn, idTrgt );

                    desc7.putReference( idnull, ref5 );

                    var idVrsn = charIDToTypeID( "Vrsn" );

                    desc7.putInteger( idVrsn, 5 );

          executeAction( idDplc, desc7, DialogModes.NO );

}

Clicking your button from the modless window successfully copies the selected layer.

As to why...

My OPINION - Photoshop is selection and state oriented. Any number of Photoshop actions may not available depending on the application's state and what is or is not selected. When attempting to do certain things from a modeless window compared to a panel - the mere presence of the modeless window changes the state of Photoshop (e.g Ps can't be the front-most window when the modeless is showing). My thinking is that the action descriptor you were using is in fact not available when a modless is showing, and is from the panel. The action descriptor code that I used evidently does not have such a restriction.

I can't state the above as fact, I am only making an educated guess based on the behaviors I have seen before and what I see in this case.

Regards

I installed the script listener, launched Photoshop. Created a document, selected and duplicated a layer. I then took the script listener output and pasted it into a js function.

Why the listener code I copied worked while yours did not (I did verify that yours does work from a panel), I think has to do with Ps' state, but I can't be certain.

Regards