-
Notifications
You must be signed in to change notification settings - Fork 392
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delaying notifications does not work in 1.0.2 #27
Comments
@billie80 Could you please tell me an example of what is the scenario because I've tried the older version and seems it doesn't work also. |
Thanks for getting back to me. First of all thank you for making this calender available to the open source community. Initially I was not aware of a setting to delay a notification. After enabling it it worked pretty well for all events I have a notification defined. I just remember that there were issues with multiple notifications. Meaning I could delay only one of them or was it none at all. Unfortunately I do not remember exactly. Sorry that I can not provide better information. However If you have more specific questions feel free to ask. |
@billie80 Thank you so much and I'm very happy that you are using Etar! |
Yes I think it is "snooze delay". I have the German translation here were it is called "Standard-Wiederholungszeit". I tried look it up in the translation strings but unfortunately the link to the translation resources from README.md does not work. |
Does this problem persist still in 1.0.4 ??? |
No, it isn't. I think this is a general problem because it happens with other calendars too. The snooze delay works fine with the popup window when the display is active. However when the screen is locked there is no popup after unlocking. There is only the notification in the status bar and delaying the event is not possible from there. |
After upgrading to 1.0.2 I am not prompted with the delay notification prompt below the notification although it is enabled in the settings with a default repeat time in the settings. This did work before in 1.0.1.
The text was updated successfully, but these errors were encountered: