-
Notifications
You must be signed in to change notification settings - Fork 19
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
Empty area at the end of the widget #67
Comments
Yes, this empty list item was added intentionally to give a visual clue that there are no more events below it. I.e. it is easier to understand that you scrolled to the bottom of the list. |
Thanks for your feedback. Personally I can live with that. But from an UX point of view, it's quite confusing. You touch an empty, colored space to get to the app settings. Imho the not so tech-savvy (or touch-safe) user wouldn't expect that. Wouldn't just a simple (colored?) line be a prefered solution? |
There are TWO main ways to get to the widget's settings:
Nobody knows what to expect from clicking on a blank area of the widget. So why not Settings? |
I too considered this a "bug," and I still do if there's not a way to turn it off. A helpful? suggestion though, I decided to "disable" it by having the future color be 100% transparent. |
Any feature that cannot be turned off is a bug for you?! I see such an opinion from time to time, regarding different apps... |
@de-es @kyledev80020 Recently I added "Max number of events" option #139 |
Thanks for coming back to this. Limiting the number of events wouldn't be my personal use case. But what about linking the empty area to the calendar intent? It would imgo be more convenient than settings. |
Hi @de-es,
Please clarify this. |
There is always an empty area at the end of the widget after the upcoming events, even when there is none upcoming. When you tab on it, it takes you to settings screen of the widget.
Is this intended or a bug? If intended, is there a setting to hide it?
Example (yellow are the upcoming events for the next day):
Using version 4.4.0
The text was updated successfully, but these errors were encountered: