error 22 window does not have a constructor

cara mengatasi photoshop error ss

Dear All,

I have been bothered by this same Photoshop error 22 when trying to use the Photomerge feature or any other of the Automate features in CS5.

My computer is a Windows 7 32bit machine but this should definitely apply to Windows 64bit machines and possibly the same logic may apply to Mac but I do not know.

I didnt find a permanent solution but I did find a temporary fix which will at least allow you to use the function for one opening of the program however if you close and reopen photoshop the problem returns.

Temporary Fix Instructions:

1.  Locate the file "Adobe Photoshop CS5 Prefs.psp" on your computer and delete it or move it elsewhere.  (I assume by doing this you may lose ass of your photoshop preferences but it will allow you to use photomerge and HDR so you choose)

2. On Windows this file can be found in the User folder under C:\**USER NAME**\AppData\Roaming\Adobe\Adobe Photoshop CS5\Adobe Photoshop CS5 Settings\ (Replace **USER NAME** with the Windows 7 account user name)

3. After deleting this file or temporarily moving it out of that folder you can then open Photoshop CS5 and use the Photomerge feature as much as you'd like.

4. As soon as you close Photoshop CS5 the program automatically makes a new Adobe Photoshop CS5 Prefs.psp file so when you try to reopen the program it will not work again.

I hope this may be helpful to some people and I hope that Adobe can fix this issue, I have not and dont plan on submitting this as a bug report to Adobe, being that I do not personally own the program (still in 30 day trial) but anyone who would like to, please feel free to do so.

UPDATE: HOW TO MAKE THIS FIX PERMANENT

If you would like to transform this fix into a permanent one you can do the following:

1. Open folder: C:\**USER NAME**\AppData\Roaming\Adobe\Adobe Photoshop CS5\Adobe Photoshop CS5 Settings\

2. Delete the "Adobe Photoshop CS5 Prefs.psp" file

3. Open Photoshop CS5.  DO NOT CLOSE IT.

4. Switch back to your window showing that folder from step 1 and now you should see a new "Adobe Photoshop CS5 Prefs.psp" but it will have a file size of 0kb because Adobe doesnt write to the file until you close the program.

5. Right-click on the file Adobe Photoshop CS5 Prefs.psp and click "Properties" and mark it as "Read Only".

6.  Now you should be able to open and close Photoshop CS5 as many times as  you'd wish and the Photomerge feature will still work, but you also  will probably not be saving any "Photoshop Preferences" if you want to  customize the program.  I dont know which preferences are saved in that  file but at the very least you can have all of the default Photoshop CS5  setting and Photomerge features working whenever you want without a  hassle each time.

Message was edited by: HSelznick

Where do I find the prefs file in WindowsXPsp3?

Becouse this error is not releted to opeationing system itself. It shows in windows and in mac. I thint, that this error is related to Windows/MAC profile files. Meaby in mac is te same. Wen I ceate second account in Windows (7-64) and run PS in this new accout, photomerge works fine.

Try, this. Meake new user account i mac. Meaby this will help as pin-point the error.

It is not releted to operating system. I'm working on Windows 7 64bit and I have this error to.

Thank you for posting this and answering it as well.  I have the same error with CS5 when invoking photomerge from bridge.  I just used this now so it is only now that I saw the problem.  (I normally use photomerge in Photoshop, not in Bridge).  So it seems to me that this is a bug in CS5 or Snow Leopard and not because we moved a script or tinkered with a scripts.  Thanks again.

This is (despite much appreciated and numerous contributions by some Adobe employees) basically a user-to-user-Forum.

So if you want to file a bug-report:

https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

Anyway, I can’t reproduce the error but this seems to concern »LatteUI.jsx« – maybe someone over at the Photoshop Scripting Forum has an idea how to fix it.

Have you edited or moved some of the concerned Scripts in any way, possibly copied them from an old version or something?