Photoshop: activeHistoryState after changing activeDocument doesn't work at all

  • 2
  • Problem
  • Updated 3 years ago
  • Solved
  • (Edited)

I have a script, which basicly changes activeDocument to doc_a, then it changes activeDocument back do doc_b and tries to check activeDocument.activeHistoryState here. It always stops executing here and I get "General Photoshop error occured. This functionality may not be available in this version of Photoshop.". Any ideas how to solve this?

The code for reproducing this bug: (I'm using CC 2015.5.1, but it doesn't work on CC 2014 either)

app.activeDocument = app.documents[0];  
app.activeDocument = app.documents[1];  
$.writeln(app.activeDocument.activeHistoryState);  
Photo of Łukasz Oślizło

Łukasz Oślizło

  • 7 Posts
  • 1 Reply Like

Posted 3 years ago

  • 2
Photo of David Dobish

David Dobish, Senior QE Photoshop

  • 197 Posts
  • 50 Reply Likes
Hello this is a bug.  Sorry.  As a work around please try this.

app.activeDocument = app.documents[0];  
app.activeDocument = app.documents[1];  
app.refresh();
$.writeln(app.activeDocument.activeHistoryState); 
Photo of Łukasz Oślizło

Łukasz Oślizło

  • 7 Posts
  • 1 Reply Like
This works, but it adds unwanted delay. Any ETA for a fix?
Photo of David Dobish

David Dobish, Senior QE Photoshop

  • 197 Posts
  • 50 Reply Likes
Yes it does add a delay.  I do not have a ETA right now.  

As a side note:

We are not seeing the error on Windows.  So you can use a Windows machine if you want to not use the app.refresh
Photo of Łukasz Oślizło

Łukasz Oślizło

  • 7 Posts
  • 1 Reply Like
Is it likely to be fixed in the next PS release?
Photo of David Dobish

David Dobish, Senior QE Photoshop

  • 197 Posts
  • 50 Reply Likes
I would say that we are looking into it.  Other than that I cannot comment on when a specific fix is coming.  Sorry to be nebulous.  
Photo of Łukasz Oślizło

Łukasz Oślizło

  • 7 Posts
  • 1 Reply Like
Thanks!
Photo of Łukasz Oślizło

Łukasz Oślizło

  • 7 Posts
  • 1 Reply Like
It looks like it's solved now. Thanks! :)
Photo of Tom Ruark

Tom Ruark, Official Rep

  • 27 Posts
  • 12 Reply Likes
Official Response
Try with CC 2017. I believe we fixed this issue.