Federated_Computer/federated-calendar
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
3,387 Commits 3 Branches 0 Tags
44092da60bb75fc7fd4f3a550ff337f7e3b1f5a9
Commit Graph
6 Commits
Author SHA1 Message Date
Georges Basile Stavracas Neto 44092da60b edit-dialog: Use GtkCalendar internally 
Instead of tracking the ESource, which is an extra
complication on top of this messy code.
 2019-10-04 00:58:41 -03:00
Michael Catanzaro 18ae67cb59 Use more g_signal_connect_object() 
Most of these are probably paranoid, not bugs. I haven't done an
exhaustive review to see what really needs it: that would be
time-consuming and require significant familiarity with the Calendar
codebase. This was just a quick check. Anyway, I vote for paranoid
when it comes to using g_signal_connect() regardless. It's dangerous,
and there's no reason to ever leave a signal connected after the user
data object has been destroyed.

Fixes #423
 2019-09-14 23:28:42 +00:00
Milan Crha a0cae4356a Port to libecal-2.0 
Fixes https://gitlab.gnome.org/GNOME/gnome-calendar/merge_requests/70
 2019-05-17 21:58:55 +02:00
Georges Basile Stavracas Neto 1c0131a55f edit-dialog: Restore time removal of all-day events 
All day events have no time period. This was a fallout from
the previous commit.
 2019-05-10 11:53:24 -03:00
Florian Latifi 6e5372189d edit-dialog: Don't convert date to timezone if all-day 
When the all-day checkbox is ticked, transforming to the
UTC timezone may change the dates of the event. On positive
timezone offsets, this happens frequently.

Fix that by only transforming to a timezone when the event
is not marked as all-day.

Fixes https://gitlab.gnome.org/GNOME/gnome-calendar/issues/338
 2019-05-10 11:49:14 -03:00
Georges Basile Stavracas Neto f55b4531ef project: Move ui-related classes to gui/ 2019-05-04 12:14:05 -03:00