Understood. 

If the speech is not being stopped by the need to play another audio, then my comment does not apply. You are doing the right thing by calling stopSpeech. No need to modify.

We're looking into it and will let you know when fixed.

Best,

Gil

Hi Pavel, we are able to recreate the problem and are working on it. I don't yet have an ETA.

I'm wondering - what is your purpose in calling stop speech after 4 seconds? Is there a special reason you need to interrupt the previous speech precisely after that delay? Or is this just a way to recreate the issue & bring it to our attention? (worked!)   

I ask, because if you simply need to interrupt one speech with another, there is no need to use stop speech for that.

Just turn ON "Interrupt Mode" setting, and any newly requested speech will be immediately launched. 

You can do so using the 'setStatus' api call, and it may work better for you.

Regardless - we will address this issue.

Best,

Gil

Apologies. 

Please use this link - 

https://sitepal.com/api/examples/react-responsive/source_code/React%20-%20Source%20Code.zip

Noted. Thanx

Hello!

We've implemented a responsive react JS example for your reference. 

In this example we positioned the SitePal character in a realistic web page, with actual content & style.

The example can be found on our support page - www.sitepal.com/support

Here is a direct link - https://sitepal.com/api/examples/react-responsive/index.html

There's a download link on the page itself (at the bottom) - where you can download the source of this page.

Please review, and see if you can use the same methodology. 

I hope this will be helpful.

Let me know how goes.

Best,

Gil

Hello Pavel - 

Our engineer tried to build your example and encountered errors - can you advise regarding - 

- version of npm and node being used on your end?

To get it to work we need to recreate your environment.

Thanx

Gil

Sure, we will look into it & advise.

Hello Pavel - 

We just deployed an update to our playback code that fixes a repeated speech/stop problem. It is most likely the same issue you describe (though the context we looked at was different).

Can you please clear your browser cache and try again - and let me know if the issue is resolved?

If you still encounter a problem we will look into it asap.

Best,

Gil