Frederik Wagner

Didn't test it, but you could try setting the ContextMenu component to a custom empty Vue component: https://newcat.github.io/baklavajs/#/styling?id=hardcore-customization

I haven't planned it for the initial release for v2, but it certainly is a nice feature so I'll add it to the roadmap. There is some transformation logic already...

Good question. Honestly, there is no elegant solution for this. You could probably hack together something with the watch functionality provided by Vue, as the position values are reactive. However,...

Sorry for the late reply, I was on vacation. This feature is planned for version 2.0. So yeah, it is on the roadmap, but unfortunately I don't think I'll finish...

This is a good point. Honestly, when I designed the engine plugin, I never had long running calculations in mind. The ability for the `calculate` function of a node to...

Thanks, I'll check as soon as I have more time and integrate that into the Engine plugin.

Yup, forgot to add `@baklavajs/events` to the dependencies. Should work now in v1.5.3

They shouldn't be needed as they will be included in the webpack-compiled build artifact. Also I can't reproduce this problem in my test projects. Can you post the error log,...

Ok yeah this happens when you use the option plugin (and probably also the renderer plugin) in TypeScript projects that don't use the `vue-property-decorator` package. Currently, the package is already...

True. This happened because I put all the events stuff in a separate package. But as you already wrote, this should change with the build process update. Thanks for mentioning...