Prevent events from disappearing with optional sticky events

[laander]

Simple, non-intrusive, fix for the common disappearing events problem (here #234 & #163 & #99 & #51). It simply allows the events to become sticky (3rd argument on renderEvent) if a property event.stick is set to true. This means that events will persistent across view changes.

[laander]

In practise, the property can be set on events whenever they are created, like so:

$scope.eventSources.push([{
  title: "Foo",
  start: // Moment time object
  end: // Moment time object
  stick: true
}])

I use it together with the select callback option on uiConfig to create temporary events by painting on the calendar canvas.

[joshkurz]

This looks a good solution, but I still don't like the fact that we have to use the stick parameter at all. It seems odd to me. I guess an event that is added after the calendar is loaded should have stick and others should not? Is that your usual workflow? When do you add stick and when don't you?

[laander]

Yes, i only use it when working with dynamic event sources where users can add/delete events after load. I've found no other way to fix the problem in that use case, and IMO, that's the only scenario where stick should be used. Do you have any other suggestions for a fix without stick?

[jkurz]

no this is the best one I have seen. Its simple, which is why I like it. I'll test it out and make sure its good. If all is well. I'll merge this in.

[laander]

Swell, let me know if you need any more from me 👍

[joshkurz]

thanks @laander

[laander]

Glad to see this happen, thanks