-
Notifications
You must be signed in to change notification settings - Fork 249
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
Blank overview window #197
Comments
This is definitely a confusing window, however I think it's just because your overview is showing a week (November 9 - 15) in which you have no activities. Is this possible? At the very least, the first time I started Hamster on a new week, I thought it had lost all my activities, but no, there were still there. One way to improve this would be to have a message at the top saying something along the lines of “No activities this week [or month, or year, or day, depending on the calendar choice] yet. Add a new activity or view last week [or month etc].” But you may be reporting a different bug entirely...
This is another bug, IMHO, noticed it as well. Reported as #198. |
Confirming that the window appears completely empty when there is no activity for the selected time span. This confused me, too. I thought that hamster was broken. Some informative message would easily solve this. |
I am using the
master
branch on Ubuntu 14.04. After a month of regular hamster usage, I rebooted my system, started hamster overview, and saw this:The overview window body does not display any text. When I open the add activity dialog the 'save' button is greyed out so I have to press enter to start tracking. It seems to track fine, and it stores new activities and offers them as choices from the drop down autocompletion menu.
Any idea why this suddenly started happening? None of my other apps, including OpenGL games, are experiencing graphical problems. I tried deleting the hamster database to no avail. Rebooting does not help either. I tried this on my laptop which also runs Ubuntu 14.04, but has an AMD card instead of my NVIDIA card, and observed the same behavior.
The text was updated successfully, but these errors were encountered: