We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'm getting this error in the console:
I am using Chrome on linux - Version 52.0.2743.82 (64-bit)
tsw.js:42 Uncaught TypeError: Cannot create property 'value' on number '0'
I found this error while looking at the online demo of Sympathetic synthesisor here
The issue seems to be caused by the face that 'reduction' is a read only float, and can't be changed, as it is in
var applySettings = function (node, settings) { for (var setting in settings) { node[setting].value = settings[setting]; } };
I have been able to fix this with the following:
var applySettings = function (node, settings) { for (var setting in settings) { if(typeof node[setting] === "object") { node[setting].value = settings[setting]; } } };
This was working for me up until recently so I guess it's just for the latest version of Chrome (Version 52.0.2743.82 (64-bit)).
The text was updated successfully, but these errors were encountered:
I am working a pull requst to fix it
Sorry, something went wrong.
Merge pull request #74 from jamespfarrell/pull-request-fix-issue-#73
07eba6a
Pull request fix issue #73
Successfully merging a pull request may close this issue.
I'm getting this error in the console:
I am using Chrome on linux - Version 52.0.2743.82 (64-bit)
tsw.js:42 Uncaught TypeError: Cannot create property 'value' on number '0'
I found this error while looking at the online demo of Sympathetic synthesisor here
The issue seems to be caused by the face that 'reduction' is a read only float, and can't be changed, as it is in
I have been able to fix this with the following:
This was working for me up until recently so I guess it's just for the latest version of Chrome (Version 52.0.2743.82 (64-bit)).
The text was updated successfully, but these errors were encountered: