2 Replies Latest reply: Oct 23, 2010 5:43 AM by - JM - RSS

    CS5 closes wrong document

    Evil Lair Community Member

      I just lost a good half hour of creative work after running into this behavior. I work fast, opening source images and flinging them into compositions, often clicking on a document window and hitting a keyboard command (like close the document) before PS has a chance to even fully switch to that window. Muscle memory has me then hitting Cancel to save changes to the source document if I made any changes before dragging it over to my composition.

       

      But this happened twice in a row today where I drag the image over to my comp, I click back on the source document and hit the command to close, the dialog pops up to save changes, but its not for the frontmost document (source) but actually for the background document (composition). I've noticed flaky things like this before but nothing to this extreme. You can see this in my screenshot below (scrubbed of content for privacy):

       

      screenshot.jpg

        • 1. Re: CS5 closes wrong document
          c.pfaffenbichler Community Member
          Muscle memory has me then hitting Cancel to save changes to the source document if I made any changes before dragging it over to my composition.

          Do you mean »not save«?

           

          Anyway, the dialog shows the name (if I understand correctly) of the document, so you were actually alerted to which document would be closed – regardless of whether the display had been refreshed.

           

          You might be better off not clicking on the window and hitting command-W but just clicking on the close-button of the window’s title bar in the first place.

          • 2. Re: CS5 closes wrong document
            - JM - Community Member

            I think there is some confusion with the name of this thread, because it details the unfortunate end result not the problem.

             

            I have seen a similar issue with CS5, where PS loses track of which file is the foremost document and is out of sync with the panels, operations etc.

             

            In the OP's case some moving quickly caused the wrong file to be closed because the commands were no longer synced with the foremost document. It has not been a persistent issue for me so I haven't pursued it further, but I believe that I have seen the behavior that the OP has experienced.