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

Switching Activities Often Leaves Sloppy Duplicates and Incorrect Activity Selection #282

Open
Zakkumaru opened this issue Nov 27, 2019 · 0 comments

Comments

@Zakkumaru
Copy link

Screenshot_20191127-Activity_Diary(c)

I am using a dumby activity to show you this bug.

  1. My database is chock-full of occurrences much like this, in which the activities don't align with timestamps correctly, and it's often multiple activities started at once and ending in different times.
  2. These are all different activities being selected, yet they all ended up as the same one.

Notice there are overlapping end times. There are many instances in my database in which there are two or three starting in the same time, as well.

This is really frustrating when trying to track different project phases and they all end up being mislabeled without a way to edit those activity numbers from within the app itself.

Possible ways to recreate:

  • Have over 5k activities in the log, causing massive lag and exponentially long load times
  • Minimizing the app without waiting a full minute or two
  • Closing the app without first waiting for over a minute
  • Changing activities without first leaving the app open for over a minute
  • Sometimes it happens anyway, even if waiting for 1~10mins with the app actively open

I have had this problem for over a year. I thought maybe once I had switched to a super high performance phone, it would compensate for the inefficient algorithms in the app. However, even after I had gone from having a nice phone to having a really nice phone (12GB RAM / Snapdragon 855 / Large storage / etc.), it still behaves very slowly and has a plethora of bugs caused by its internal algorithms which can't be switched off.

It would appear to me that instead of simply inserting a new activity into the log, which you would expect from a seemingly simple app, it also changes the most recent entry to be whatever is still stuck as the currently-selected tile. Meaning, the algorithm takes so long to switch to whatever activity is selected as next that it updates the activities to be whatever was previously selected.

If none of that makes sense, I will try to explain in more detail.

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

No branches or pull requests

1 participant