You are on the right track with
this.$emit(). You need to create methods that fire the
this.$emit() method so you can “pass” information up to the parent. In other words, instead of inline methods, create methods which will do the communicating up to the parent component with
this.$emit(). Those emits (as you build them) become the events available to use on the parent. Props down - events up.
You can’t return, because QDialog is an object with functions and not a function itself.
Is this kind of what you are looking for?
Um, I think you might be using the wrong technologies in general or missunderstanding what vtk.js is supposed to be used for then. vtk.js is built for running in the browser. As their docs say…
What is vtk.js?
vtk.js is a rendering library made for Scientific Visualization on the Web. It adapts the VTK structure and expertise to bring high performance rendering into your browser.
Why getting worried? Worried about what?
Um, I don’t know vtk.js, but being it is OpenGL I’d say you’ll not get it working with out some real trickery on the server (with SSR).
You might try putting whatever component you are using to integrate vtk.js with in a QNoSSR component.
Or, just drop the idea of using SSR. Why would you need it for such a graphical interface?