Hi,
With the 13 november build I noticed that events which I add with an explicit call to addEvent are not shown. After debugging I can see that the eventwindow gets created but it is never rendered, the callstack:
addEvent
retagOverlapRange
then this is called:
var events = this.findEventsInRange(start, end, lane, this.data);
this.data is not an array of events but it is the dayView data, which I think does not work for findEventsInRange as no events are returned.
Then within findEventsInRange function there is this call:
var events = this.findOverlappingEvents(range, range, false, useLane, data);
with the parameter false so that the event which just got added is not returned, the events is empty and nothing gets rendered, it seems.
I tried to see if this can be reproduced in an example from the feature explorer but in the 13-11 build I can't add events in the example calendars, there is a jscript error (see the attached screenshot, the new window is created in the top-left).
gr. Martin
With the 13 november build I noticed that events which I add with an explicit call to addEvent are not shown. After debugging I can see that the eventwindow gets created but it is never rendered, the callstack:
addEvent
retagOverlapRange
then this is called:
var events = this.findEventsInRange(start, end, lane, this.data);
this.data is not an array of events but it is the dayView data, which I think does not work for findEventsInRange as no events are returned.
Then within findEventsInRange function there is this call:
var events = this.findOverlappingEvents(range, range, false, useLane, data);
with the parameter false so that the event which just got added is not returned, the events is empty and nothing gets rendered, it seems.
I tried to see if this can be reproduced in an example from the feature explorer but in the 13-11 build I can't add events in the example calendars, there is a jscript error (see the attached screenshot, the new window is created in the top-left).
gr. Martin
Attached Files
Comment