- 问题7.png (160.98 KiB) Viewed 4906 times
- 问题8.png (64 KiB) Viewed 4906 times
Support Forum
Hello.
I assume that problem is caused by using scheduler bundle as module (using import). Try to just load it on the page, old style? Script tag or some config for webpack to compile our bundle into your app.
When you will resolve that issue, you will face more, related to incorrect usage.
Scheduler at the moment doesnt support reconfiguring all columns at once
I see at least two options here:
1) store not the instance, but class:
2) import class in vue component as such:
Let us know about the result!
I assume that problem is caused by using scheduler bundle as module (using import). Try to just load it on the page, old style? Script tag or some config for webpack to compile our bundle into your app.
When you will resolve that issue, you will face more, related to incorrect usage.
Scheduler at the moment doesnt support reconfiguring all columns at once
// main.js
// you instantiate empty scheduler that is not rendered anywhere
Vue.prototype.$scheduler = new Scheduler({})
// Scheduler.vue
this.$scheduler.setConfig(config) // you overwrite configs here, including columns
this.schedulerEngine = this.$scheduler
1) store not the instance, but class:
// main.js
Vue.prototype.$scheduler = Scheduler
//scheduler.vue
this.schedulingEngine = new this.$scheduler(config)
var bryntum = require('../../lib/scheduler/scheduler.umd.js')
this.schedulerEngine = new bryntum.Scheduler(config)