Skip to content
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

Timeline (barchart) view does not cap off at 1h, but extends to 2h. #851

Open
2 tasks done
pringithub opened this issue Mar 2, 2023 · 5 comments · May be fixed by ActivityWatch/aw-webui#599
Open
2 tasks done

Timeline (barchart) view does not cap off at 1h, but extends to 2h. #851

pringithub opened this issue Mar 2, 2023 · 5 comments · May be fixed by ActivityWatch/aw-webui#599

Comments

@pringithub
Copy link

  • I am on the latest ActivityWatch version.
  • I have searched the issues of this repo and believe that this is not a duplicate.
  • Ubuntu 20.04 LTS 5.15.0-60-generic:
  • ActivityWatch version v0.12.1:

Describe the bug

The Timeline (barchart) view does not cap off at 1h, but extends to 2h.

To Reproduce

Go to Activity tab, work for over an hour, and observe

Expected behavior

barchart should cap at 1h

Documentation

image

Additional context

@github-actions
Copy link

github-actions bot commented Mar 2, 2023

Hi there!
As you're new to this repo, please make sure you've used an appropriate issue template and searched for duplicates (it helps us focus on actual development!). We'd also like to suggest that you read our contribution guidelines and our code of conduct.
Thanks a bunch for opening your first issue! 🙏

@BelKed
Copy link
Contributor

BelKed commented Mar 2, 2023

I can reproduce this issue on my installation...
Probably it's related to #724.


Screenshot

@8Dion8
Copy link

8Dion8 commented Jul 19, 2024

Would just setting a fixed y-axis of 1hr fix the issue? At least visually. Seems like a simple fix until the bigger issue of accuracy is resolved, there's no point in making the y-axis dynamic.

@morhadi
Copy link

morhadi commented Dec 9, 2024

It has been more than a year, this issue still exists even though the pr has no conflicts and is still open.
Can anyone explain?

@8Dion8
Copy link

8Dion8 commented Dec 9, 2024

@morhadi the pr introduces other issues which I just haven't gotten around to, it's in the PR comments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants