You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/bug_report.yml
+9-6Lines changed: 9 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
name: Bug Report
2
-
description: Help improve Reminders by filing a bug report
2
+
description: Help improve Cue by filing a bug report
3
3
title: "[Bug]: "
4
4
labels: ["bug"]
5
5
body:
@@ -8,26 +8,27 @@ body:
8
8
value: |
9
9
## System information
10
10
11
-
Make sure you have tested the Flatpak release of Reminders through Flathub before opening a bug report. If the bug is not present in the Flatpak open the report with the package maintainer.
11
+
If on Linux, make sure you have tested the Flatpak release of Cue through Flathub before opening a bug report. If the bug is not present in the Flatpak open the report with the package maintainer.
12
12
13
13
- type: dropdown
14
14
id: package
15
15
attributes:
16
16
label: Package
17
17
description: |
18
-
Where did you install Reminders from?
18
+
Where did you install Cue from?
19
19
options:
20
20
- Flathub
21
21
- Flathub Beta
22
+
- Windows Store
22
23
validations:
23
24
required: true
24
25
25
26
- type: input
26
27
id: distro
27
28
attributes:
28
-
label: Distribution
29
+
label: OS
29
30
description: What distribution are you currently using?
placeholder: Fedora 37, Ubuntu 22.04, Windows 10...
31
32
validations:
32
33
required: true
33
34
@@ -63,7 +64,9 @@ body:
63
64
attributes:
64
65
label: Logs
65
66
description: |
66
-
If you saw an error dialog, click view error and copy the text here. Otherwise you can run something like `sudo journalctl --boot | grep remembrance | grep -i error` in the terminal to see the errors and copy that here.
67
+
If you can access the about page, you can also view logs by going to About > Troubleshooting > Debugging Information.
68
+
On Windows you can find these logs by pressing `Windows Key + r` and entering `%LOCALAPPDATA%`, and then navigating to `cuedevs.Cue.Devel_4zhcwx3m88y16\LocalState\cue`.
69
+
On Linux the logs are at `~/.var/app/io.github.cuedevs.Cue/data/cue`.
Currently this is only packaged with Reminders and anyone who wants to use it will have to have the full Reminders app installed. The reason this exists is to allow integrating the Reminders app with desktop environments through extensions.
9
4
@@ -13,6 +8,30 @@ This service will have some breaking changes made to it at times, so make sure y
13
8
14
9
Newer versions of this service should usually be compatible with apps that expect an older version. If this ever changes, the bus name will be updated.
15
10
11
+
To use the dbus service, you first need to connect to the public service on the DBus session bus, and get the private address, and then connect to the private server at that address. This is done for security reasons, and also for performance reasons on Windows. I wont be explaining how to do all of this in your app, but you can always look at my source code if you are confused, and GLib also has an example [here](https://gitlab.gnome.org/GNOME/glib/-/blob/HEAD/gio/tests/gdbus-example-server.c).
12
+
13
+
Do not try to use this service on Windows, you probably will not have any luck even though Cue runs on Windows.
14
+
15
+
# Public Service (Session Bus)
16
+
name: io.github.cuedevs.Cue.Service
17
+
18
+
interface: io.github.cuedevs.Cue.Service
19
+
20
+
object: /io/github/cuedevs/Cue/Service
21
+
22
+
## Methods
23
+
24
+
### GetPrivateAddress
25
+
Get address of private dbus server
26
+
- Returns (s)
27
+
- dbus-address
28
+
- Type: s
29
+
30
+
# Private Service
31
+
interface: io.github.cuedevs.Cue.Service
32
+
33
+
object: /io/github/cuedevs/Cue/Service
34
+
16
35
## Enums
17
36
### RepeatType
18
37
On what interval to repeat the reminder.
@@ -41,18 +60,18 @@ Type: a{sv}
41
60
| 'id' | s | This is the id of the reminder. | This usually cannot be left blank, no default. |
42
61
| 'title' | s | This is the title of the reminder. | '' |
43
62
| 'description' | s | This is a short description of the reminder. | '' |
44
-
| 'due-date' |u| This is a Unix timestamp for the day that the reminder is due. This should be at 00:00 of the desired day in UTC, and can be 0 if you don't want to set a due date. | 0 |
45
-
| 'timestamp' |u| This is a Unix timestamp that sets when the notification will be sent. This has to be on the same day as the due date, and if it isn't the due date will be changed. This can be 0 if you don't want to send a notification. | 0 |
63
+
| 'due-date' |t| This is a Unix timestamp for the day that the reminder is due. This should be at 00:00 of the desired day in UTC, and can be 0 if you don't want to set a due date. | 0 |
64
+
| 'timestamp' |t| This is a Unix timestamp that sets when the notification will be sent. This has to be on the same day as the due date, and if it isn't the due date will be changed. This can be 0 if you don't want to send a notification. | 0 |
46
65
| 'important' | b | Whether or not the reminder is important. | False |
47
66
| 'completed' | b | Whether or not the reminder is completed. | False |
48
67
| 'repeat-type' | q | This is the enum [RepeatType](#repeattype). | 0 |
49
68
| 'repeat-frequency' | q | How often to repeat the reminder, so if 'repeat-type' is 4 and and 'repeat-frequency' is 3, it will repeat every 3 weeks. | 1 |
50
69
| 'repeat-days' | q | This is the enum [RepeatDays](#repeatdays). | 0 |
51
70
| 'repeat-times'| q | How many times in total the reminder should be repeated, this gets decreased by 1 each time the reminder is repeated. -1 if you want to repeat forever or are not repeating. Must be -1 for Microsoft Tasks. | -1 |
52
-
| 'repeat-until' |u| This is a Unix timestamp that represents the last day that the reminder should be repeated on. This should be at 00:00 of the desired day in UTC. Must be 0 for Microsoft Tasks | 0 |
53
-
| 'created-timestamp' |u| This is a Unix timestamp that represents the time the reminder was created, this is set automatically and cannot be changed. | 0 |
54
-
| 'updated-timestamp' |u| This is a Unix timestamp that represents the last time the reminder was updated, this is set automatically and cannot be changed. | 0 |
55
-
| 'completed-date' |u| This is a Unix timestamp that represents the day the reminder was completed, at 00:00 in UTC. 0 if not complete. This is set automatically and cannot be changed. | 0 |
71
+
| 'repeat-until' |t| This is a Unix timestamp that represents the last day that the reminder should be repeated on. This should be at 00:00 of the desired day in UTC. Must be 0 for Microsoft Tasks | 0 |
72
+
| 'created-timestamp' |t| This is a Unix timestamp that represents the time the reminder was created, this is set automatically and cannot be changed. | 0 |
73
+
| 'updated-timestamp' |t| This is a Unix timestamp that represents the last time the reminder was updated, this is set automatically and cannot be changed. | 0 |
74
+
| 'completed-date' |t| This is a Unix timestamp that represents the day the reminder was completed, at 00:00 in UTC. 0 if not complete. This is set automatically and cannot be changed. | 0 |
56
75
| 'list-id' | s | This is the id of the list that the reminder is in. | 'local' |
57
76
58
77
## List Object
@@ -182,12 +201,12 @@ Add a new reminder
182
201
- Note that the 'completed', and 'id' key will be ignored here
183
202
- You can leave any of these values blank, in that case the default value will be used
184
203
185
-
- Returns (su)
204
+
- Returns (st)
186
205
- reminder-id
187
206
- Type: s
188
207
- Id that was generated to represent the reminder, keep track of these
189
208
- created-timestamp
190
-
- Type: u
209
+
- Type: t
191
210
- The Unix timestamp of when the reminder was created
192
211
193
212
### UpdateReminder
@@ -200,9 +219,9 @@ Update an existing reminder
200
219
- Note that the 'completed' key will be ignored here
201
220
- You can leave any of these values blank, in that case the previous value will be used
202
221
203
-
- Returns (u)
222
+
- Returns (t)
204
223
- updated-timestamp
205
-
- Type: u
224
+
- Type: t
206
225
- The Unix timestamp of when the reminder was updated
207
226
208
227
### UpdateCompleted
@@ -217,12 +236,12 @@ Update the completed status of a reminder
217
236
- Type: b
218
237
- Whether or not the reminder should be completed
219
238
- completed-date
220
-
- Type: u
239
+
- Type: t
221
240
- The Unix timestamp of the day the reminder was completed
222
241
223
-
- Returns (u)
242
+
- Returns (t)
224
243
- updated-timestamp
225
-
- Type: u
244
+
- Type: t
226
245
- The Unix timestamp of when the reminder was updated
227
246
228
247
### RemoveReminder
@@ -245,12 +264,12 @@ Update an existing reminder
245
264
- Note that the 'completed' key will be ignored here
246
265
- You can leave any of these values blank, in that case the previous value will be used
247
266
248
-
- Returns (u)
267
+
- Returns (t)
249
268
- updated-reminder-ids
250
269
- Type: as
251
270
- Ids of reminders that were actually updated (in case there were errors)
252
271
- updated-timestamp
253
-
- Type: u
272
+
- Type: t
254
273
- The Unix timestamp of when the reminder was updated
255
274
256
275
### UpdateCompletedv
@@ -265,15 +284,15 @@ Update the completed status of a reminder
265
284
- Type: b
266
285
- Whether or not the reminder should be completed
267
286
268
-
- Returns (asu)
287
+
- Returns (ast)
269
288
- updated-reminder-ids
270
289
- Type: as
271
290
- Ids of reminders that were actually updated (in case there were errors)
272
291
- updated-timestamp
273
-
- Type: u
292
+
- Type: t
274
293
- The Unix timestamp of when the reminder was updated
275
294
- completed-date
276
-
- Type: u
295
+
- Type: t
277
296
- The Unix timestamp of the day the reminder was completed
278
297
279
298
### RemoveReminderv
@@ -359,7 +378,7 @@ Read reminders file again and also check for remote updates. Changes will be emi
359
378
- The version of the service that is currently loaded (PEP 440)
360
379
361
380
### Quit
362
-
Quits the service
381
+
Quits the service, this will not return anything and will close the connection immediately. Make sure to handle the error if needed.
363
382
364
383
## Signals
365
384
@@ -411,7 +430,7 @@ Emitted when a Reminder is created or updated
411
430
412
431
### CompletedUpdated
413
432
Emitted when a reminder's completed status is changed
414
-
- Parameters (ssbuu)
433
+
- Parameters (ssbtt)
415
434
-[app-id](#app-id-parameter)
416
435
- Type: s
417
436
- reminder-id
@@ -421,10 +440,10 @@ Emitted when a reminder's completed status is changed
421
440
- Type: b
422
441
- Whether or not the reminder was set as completed
423
442
- updated-timestamp
424
-
- Type: u
443
+
- Type: t
425
444
- The Unix timestamp of when the reminder was last updated
426
445
- completed-date
427
-
- Type: u
446
+
- Type: t
428
447
- The Unix timestamp of the day the reminder was completed
429
448
430
449
### ReminderRemoved
@@ -446,7 +465,7 @@ Emitted when a reminder is removed
446
465
447
466
### RemindersCompleted
448
467
Emitted when multiple reminders' completed status changes
449
-
- Parameters (saa{sv})
468
+
- Parameters (sasbtt)
450
469
-[app-id](#app-id-parameter)
451
470
- Type: s
452
471
- reminder-ids
@@ -456,10 +475,10 @@ Emitted when multiple reminders' completed status changes
456
475
- Type: b
457
476
- Whether or not the reminders were set as completed
458
477
- updated-timestamp
459
-
- Type: u
478
+
- Type: t
460
479
- The Unix timestamp of when the reminders were updated
461
480
- completed-date
462
-
- Type: u
481
+
- Type: t
463
482
- The Unix timestamp of the day the reminders were completed
0 commit comments