Replies: 1 comment
-
I'll answer myself. So obviously, the Opencascade.js version used in the current CascadeStudio often has different method names, which makes it impossible to use the more recent kernel "as is". I'll re-map the method calls in my forked version, but many thanks all CascadeStudio contributors for the great initial idea! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi! I'm new to both JS language and node.js, so I kindly ask for some help and explanation. If I just clone the repo, enter the project folder (on master branch) and start VSCode live server, everything is working more or less as expected (I found at least one issue, but will ask about it later, possibly update could help). If I do
npm update
(the output:) , or fix the versions in the
package.json
to the minimum ones an donpm update
, or manually replace the Opencascade module folder to a later version (e.g. tried with one of 2.0.0betas), the CascadeStudio gets stuck at loading the kernel. Is it anyhow possible to safely update the OCC version? ThanksBeta Was this translation helpful? Give feedback.
All reactions