Performance problem

[Dirli]

after adding PR (#232), I noticed a few bugs

1. when scrolling through months, if you go far enough (for example, in 1999), you notice increased memory consumption

this is because the array of months is not cleared. after closing the widget, everything remains in memory.

2. when switching to a new month, a lot of unnecessary actions are performed.

The calendar model changes 4 times (per iteration), each time it completely redraws everything related to events.

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[fs3o5]

1. Are you sure this issue is related to this PR? The calendar data is still stored in the same way. The calendar data should probably still be cleared after some time/when closing the widget.

2. The months are changed so often because the next calendar page needs to be drawn before it is switched to. It might still be a good idea to change that.

[Dirli]

1 carousel is a gtk.container, you fill it (when to switch new months for a long time), but you don't remove it from it. when closing, nothing is cleared on its own
2 it's not your problem, you're singleton's hostage, need to change the calendar_model. you can't use singleton anymore (it's better not to use it at all)