When the program runs after a restart, it tags your missed pings with “afk off RETRO”, but these weren’t being synced to the cloud. This has now been fixed.
Also, when importing an old log via the Log Viewer, it now automatically fixes / reformats your old log file before uploading it to the cloud.
These were the last real changes that I wanted to personally do, and I feel like the program is in a good spot. I probably won’t be making any further changes unless I get feature requests or bug fixes from y’all.
@CortTheWart, I promised to try the updated version, so here I am reporting back, sorry it took a while.
Unfortunately, I can’t get it to work at all. I made a clean install and made sure that all libraries/resources are installed to pip as well. Here’s what I am getting when I try to see settings or log:
If it’s working for you and everybody else, though, it’s probably not worth the time to debug it to get it to work for me right now.
EDIT: just to confirm that nothing of mine has been running in parallel (I noticed previously that the previous version and my scripts were preventing one another from opening pop-ups). The pop-up that asks for tag at ping wouldn’t open either, but after some time the ping is entered into the log as AFK.
I’m pretty sure I fixed it, so try to do a clean install now.
very weird bug, as I tried a fresh install on my main computer, and it was working fine, but then doing the exact same thing on my laptop and the windows weren’t opening. Took me awhile to debug it on my laptop, but I figured out what was causing it, and what is weird is that it’s something that I shouldn’t have needed to change since it worked in every other version + my current version but seemingly only on my computer. Try it now and let me know how it goes, should be fine.
Thanks for so promptly fixing whatever the bug was. I was able to install it, now waiting for pings to test how everything works
Is the Android version in the other thread the most up-to-date one? as I am trying to look at the two together.
The android version in the other thread is not the most up-to-date one. The most recent one is in the testing phase, with only a few days left before I can publish it to the Play Store, but if you want to access it early you can DM the email you use for the play store, and I can add you to the list of testers so you can download it.
I just linked to the other thread in the help doc for the TagTime integration so we should probably edit that to point to the latest version or how to get added to the beta for the latest version.
(I’m getting value out of it myself, btw! But so far just as a way to record certain pings when afk that I manually copy to the desktop TagTime when I’m back at a computer.)
Sorry for the late reply, been in the hospital as I had another lung collapse.
Last time I checked, I wasn’t able to edit the original post. I do believe I need to update the apk link as it might be one version behind, but I can also add instructions on how to get added to the beta, but it requires me to have their email in order to add them to the beta. What would you think the best way to do that would be? Maybe a google form? Or just say that they should DM me? Let me know.
I’m glad to hear that you’re getting value out of the android app, but may I ask why you feel the need to manually copy over the pings to the desktop app, instead of just syncing the data? Any feedback helps. I do plan on adding a simple notifications on/off button on the home page of the android app, which could maybe help in this case, AKA easily having notifications turned off on your phone while running TagTime on desktop, and then turning the notifications back on when you go afk.
Oh no! Really sorry to hear you’ve been in the hospital. The forum permissions are a bit of a mystery but just DM me when it’s not letting you do something and I’ll either figure out the permissions or make the change for you.
Maybe it’s worth making the google forum, just to capture the people too shy to DM?
Well, it’s reasonably rare that I’m copying pings from my phone to my laptop and I wasn’t sure if the way the android app syncs to a beeminder goal is compatible with the way the old desktop version does it.
PS, feature request, if you agree with it: Ditch the save and submit buttons. I.e., every ping immediately goes into the log and any change to the tags is immediately/automatically saved. That also means you can always count on the log being up to date with the latest ping that has pung.
As for notifications, I actually like the redundancy of having both phone and desktop ping.
I’m assuming the old desktop version makes a datapoint like one of these
The android app and my desktop version add the ping as a datapoint like the second image above, although that can be changed to have it remove the “1 ping:” part until more pings get added on the same day. Regardless, when a second ping gets added, it updates the same datapoint to this:
I believed the old desktop app just creates a new datapoint entirely even if it’s on the same day.
In our original discussion of this same thread, this was recommended to be the better way to go about adding multiple pings to a beeminder goal, AKA merging pings, so that’s the way I went with.
It should be technically compatible with the old desktop version, but it would just update the most recent datapoint of the day, and then if you were to add more pings on the desktop version, the android app would just update the newest up-to-date datapoint of the day. Let me know if that all makes sense, I’m just trying to describe how it deals with beeminder goals, and if there’s anything I could change to make it more compatible with the old version, let me know on that as well.
From a consumer standpoint, it’d be weird like this and I would say people would feel like they don’t know if their pings are getting saved. Say you click on the notification to enter your pings, you’re still gonna have to click a button to get off of the menu, basically saying “I’m done entering my ping”, and if I removed the submit button it would literally just be the back arrow button, which doesn’t entirely make sense. The other way I would see it is that when you just press Enter on your keyboard, it submits the ping, but this is already the case, you can either press the button or use the Enter key on your keyboard, and I should also mention that people will usually be clicking the Tag buttons to quickly enter their ping, and the keyboard doesn’t pop up for this, so the submit button is there. It could make sense in the log editor where you edit your log and then back out, but in the main ping page, I definitely wouldn’t do this.
The OG app behaves like yours, updating existing datapoints. It uses a local cache file for each goal to keep from comparing the whole goal history every time.
I’d keep the 1 ping: prefix in case someone ever wants to download the datapoints from the goal and parse the comments.
I could’ve sworn it always created a new datapoint, maybe I’m thinking about the OG android app? Or it not merging properly from the desktop app and the android app? Was it not the case where if you inputted a ping from the OG desktop app, and created a datapoint like “1 ping: goal1 desktop”, and then you inputted a ping from the OG android app, it would create a new datapoint like “1 ping: goal1 android” instead of merging them like “2 pings: goal1 desktop, goal1 android”?
Ah, yes, thanks @philip and @scarabaea for clarifying about OG desktop vs OG Android app.
As for the buttons for submitting and saving pings: Makes sense about wanting a button for “I’m done picking tags”. Maybe the best of both worlds could be that instead of a “Submit” button it’s a “View Log” button?
I guess when I click a notification and choose some tags, the thing I then want confirmation of is that I’m caught up. So I want to see the log and see that I’ve answered everything. And I think what throws me off the most is that it’s possible to view the log without it showing the latest pings.
And then secondary to that, I think that if I change the tags on a previously answered ping, every change I make should auto-save.
PS: Another thing I just noticed: I think the forward/back arrows on the individual ping view are reversed. I’m expecting to go forward in time when I click the arrow on the right.
I also feel like it would be more convenient like that. I mean, I personally can work around that, but if we are testing and sharing our impressions here to improve the general user experience, that’s one of the aspects.
@dreev
I get that, what I will do is maybe say “Save Ping” / “Answer Ping” for the button, and then have it automatically direct the user to the logs.
I’ll also make it so that when you get a notification, it will automatically add the ping into your log, maybe with “afk RETRO”, and then if you end up answering the notification, it will edit that ping. Currently it will just add “missed” pings plus the latest ping after you answer the latest notification, which I can see doesn’t make too much sense.
I could implement this, i’m fine with removing the save button in the log editor, and just checking to see if anything changed when you end up either going back or to another ping.
@scarabaea does this make sense to you? is this how it is done in the OG android app too? I personally feel like logically it makes sense that in a top-down list, going “forward” is essentially going down the list, but let me know what you think.
Yes, all these solutions you outlined seem like something that will make the user experience more intuitive.
As for right/left, I don’t have a strong opinion. In the OG Android app it is the other way around than in your current implementation, but I think it comes to getting used to the arrows going one way or the other, rather than a strong internal logic why it would only be intuitive this or that way.
If people are transferring over from the OG app, I’d rather just have those arrows be the same cause there’s no logical reason to have them switch over and get used to it. So I’ll flip those arrows too
