• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers

P: ActiveHistoryState after changing activeDocument doesn't work at all

2 Votes
Community Beginner ,
Aug 22, 2016 Aug 22, 2016

Copy link to clipboard

Copied

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);  
Bug Fixed
TOPICS
macOS , Windows

Views

42

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Nov 03, 2016 Nov 03, 2016
Try with CC 2017. I believe we fixed this issue.

Votes

Translate

Translate
9 Comments
Adobe Employee ,
Aug 22, 2016 Aug 22, 2016

Copy link to clipboard

Copied

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); 

Votes

Translate

Translate

Report

Report
Community Beginner ,
Aug 22, 2016 Aug 22, 2016

Copy link to clipboard

Copied

This works, but it adds unwanted delay. Any ETA for a fix?

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Aug 22, 2016 Aug 22, 2016

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

Report
Community Beginner ,
Aug 22, 2016 Aug 22, 2016

Copy link to clipboard

Copied

Is it likely to be fixed in the next PS release?

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Aug 22, 2016 Aug 22, 2016

Copy link to clipboard

Copied

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.  

Votes

Translate

Translate

Report

Report
Community Beginner ,
Aug 22, 2016 Aug 22, 2016

Copy link to clipboard

Copied

Thanks!

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Nov 03, 2016 Nov 03, 2016

Copy link to clipboard

Copied

Try with CC 2017. I believe we fixed this issue.

Votes

Translate

Translate

Report

Report
Guest
Nov 03, 2016 Nov 03, 2016

Copy link to clipboard

Copied

Good

Votes

Translate

Translate

Report

Report
Community Beginner ,
Nov 12, 2016 Nov 12, 2016

Copy link to clipboard

Copied

LATEST
It looks like it's solved now. Thanks! 🙂

Votes

Translate

Translate

Report

Report