CEP panels

[danielg38016284]

Hello there,

I am trying to send some data from JSX to JS, but the async operations are unreliable.

I return from JSX a folder path and then I try to commit a mutation to vuex, but it works like a lottery...

I tried using promises with no result. I increased the timeout to 1000 but it also kinda doesn' work all the time.

[Guest]

Moving to Photoshop Scripting from Photoshop

[Geppetto Luis]

Better if placed in this forum

https://forums.adobe.com/community/creative_cloud/add-ons/extensions/content

[Ten A]

In this case, You can use PlugPlugInterface.

You can reference below sample.

CreativeSuiteSDK_Experimentals/net.sytes.chuwa.callbacktest at master · ten-A/CreativeSuiteSDK_Exper...

[sberic]

First off, it is important to note that the evalScript function has some consistency issues when it comes to its classification as "asynchronous".

Second, why are you using $nextTick outside of the callback? Why not simply commit to the Vuex store in the evalScript completion callback?

chooseExportPath() {
     const cs = new CSInterface();
     // Call JSX for folder path
     cs.evalScript("choosePath()", (result) => {
          const exportPath = document.getElementById('pathExport');
          exportPath.value = result;
          this.$store.commit('setExportPath', result);
     });
}

Notes:

1. Using the arrow function allows you to capture the "this" Vue instance from the calling context. No need to create a reference to it (vm) to maintain the context.
2. With this approach you cannot set the value incorrectly by guessing at the timing as you only attempt to set the value when you know you have it.
3. You probably don't need to use $nextTick at all. Vuex is supposed to handle the asynchronous updates of your state modifications anyway. Unless there's a specific reason to do so (which you wouldn't have mentioned...) then setting it directly as above is simple, straightforward, and easier to understand.