aboutsummaryrefslogtreecommitdiff
path: root/src/actions.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Add option to show/hide alarmskugiigi2023-12-191-1/+4
|
* Fix cppcheck errors/warningsRobert Tari2022-02-081-5/+9
|
* Detect desktop to launch applications.Renato Araujo Oliveira Filho2021-08-291-44/+20
|
* Make sure that the ocurrence time is used to build the url to launch ↵Renato Araujo Oliveira Filho2021-08-291-14/+15
| | | | external application.
* Fix calendar going into update loopRobert Tari2020-07-261-4/+8
|
* URL dispatcher support: Build phone code, even if URL dispatcher is unavailable.Mike Gabriel2018-03-261-4/+1
|
* Make the datetime indicator build on non-Ubuntu systems (which mostly lack ↵Mike Gabriel2017-12-081-2/+4
| | | | url-dispatcher and Ubuntu Touch sound schema files.
* Fork ayatana-indicator-datetime from Ubuntu's indicator-datetime.Mike Gabriel2017-05-171-2/+2
|
* in Actions, sync DateTime API use by calling DateTime::Local(time_t) instead ↵Charles Kerr2015-04-061-2/+2
| | | | of DateTime::DateTime(time_t)
* fix GAction leakage found while testing new unit tests with valgrindCharles Kerr2015-03-141-0/+8
|
* use the new DateTime::start_of_day() and DateTime::start_of_minute() functions.Charles Kerr2015-03-141-3/+1
|
* Change the desktop menu's settings menuitem's label to match the spec. ↵Charles Kerr2014-03-241-48/+68
|\ | | | | | | Fixes: 1296585
| * make the phone and desktop actions more consistent with each other; eg, ↵Charles Kerr2014-03-221-48/+68
| | | | | | | | 'indicator.desktop.open-calendar-app' + 'indicator.phone.open-calendar-app'
| * give 'phone' and 'desktop' their own action namespaces. Fix documentation on ↵Charles Kerr2014-03-211-2/+2
| | | | | | | | 'activate-settings', since there are two forms of it, one for phone and one for desktop.
* | when clicking onto a different calendar date on the Desktop, show the events ↵Charles Kerr2014-03-201-1/+4
|/ | | | for that calendar day starting at the beginning of the day, rather than the current time of day.
* decouple the planner's states; need three separate sets: upcoming-now (for ↵Charles Kerr2014-03-091-6/+7
| | | | alarms in the current time), upcoming-calendar (to show events coming from the selected calendar date), and calendar-month (all the appointments in the month displayed in the menu).
* copyediting: as per review, use name_of_thing() instead of ↵Charles Kerr2014-01-301-2/+2
| | | | get_name_of_thing() or getNameOfThing()
* as per review, constify getters where possible. This isn't always possible ↵Charles Kerr2014-01-301-3/+3
| | | | due to system APIs asking for non-const pointers.
* as per review, don't inline gettersCharles Kerr2014-01-301-0/+11
|
* sync with lp:~larsu/indicator-datetime/reset-date and add corresponding unit ↵Charles Kerr2014-01-291-3/+17
| | | | tests.
* sync the exported calendar state with the #State backendCharles Kerr2014-01-251-2/+28
|
* fix r325 regression found by test-menusCharles Kerr2014-01-221-2/+2
|
* get timezone, clock tests running again with Settings & StateCharles Kerr2014-01-161-3/+3
|
* Plug the Settings object into the State container s.t. menus and actions can ↵Charles Kerr2014-01-161-2/+2
| | | | update themselves when the user's settings change.
* Function: add fully-tested ActionGroups, per-profile Menus, state object.Charles Kerr2014-01-141-0/+215
Form: Add code annotations/comments. Remove dead code. Use Mir style guide. Todo: GSettings toggles, sync with new dbus-test-runner API, get GNOME Panel building again