Hi,
With Google Chrome I have a bug but it’s hard to explain.
The sample code in designer below doesn’t reproduce the bug but shows the idea of custom events with another call to scheduler.parse() to load some data.
Here are my steps:
- initialize the scheduler on the page, in timeline mode.
- load JSON data from server, transform it to custom classes (as below)
- call scheduler.parse() with this data
- edit a new event data in a custom form on interface
- make a server call to save data
- load again JSON data from server, transform it to custom classes
- call scheduler.clearAll()
- call scheduler.parse() with this data, as I understood there will be data added and overwritten in scheduler internal map, but since event ids haven’t changed and are all unique, no bothering
- click on an event, often the “onClick” behavior isn’t triggered. In fact, it is triggered for only some existing events on the scheduler, I haven’t catched the logic yet.
- no bug with another browser than Chrome…
Thanks for any idea. Is there some bug with DOM not being ready?
At office, we use both Dhtmlx Suite 4.2.1 for everything and Dhtmlx Scheduler 4.3.1 for scheduler.
scheduler.attachEvent("onClick", function(eventId, native_event_object) {
console.info("clicked on event ", eventId);
});