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

Workflowy tasks counted twice from different machines #75

Open
JMTyler opened this issue Sep 10, 2013 · 3 comments
Open

Workflowy tasks counted twice from different machines #75

JMTyler opened this issue Sep 10, 2013 · 3 comments
Labels

Comments

@JMTyler
Copy link

JMTyler commented Sep 10, 2013

I've noticed that the HabitRPG extension will retroactively count completions from Workflowy when I open its tab, even if it wasn't there when I actually completed the item. I think this is a great feature, mainly because I have a Workflowy chrome extension as well (which HabitRPG doesn't pick up on, as I would expect), so it's nice that I can complete tasks there quickly but still open a tab once a day to have HabitRPG take notice.

However, it doesn't work well with multiple computers. If I complete a Workflowy task from one computer, then HabitRPG will give me XP for it... but then as soon as I open the tab on my second computer, HabitRPG gives me XP again.

I understand that this might be a time-consuming thing to fix, since you're probably just watching for changes right now, and to fix it you'd have to actually record Workflowy's item IDs (assuming that's even available to you...) so I want to be clear that it's not a big deal. Just wanted to make you aware of it.

Cheers, and I hope eventually I might have some time to contribute to this too!

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@lefnire
Copy link
Contributor

lefnire commented Sep 10, 2013

Great idea, and lots of other things I personally want to add around Workflowy (eg, I delete tasks when I'm done - not check them off, so I want points for deletion). But heads up - nobody's currently working on the Chrome Extension unfortunately. We're looking for maintainers. We'll probably be able to jump back in in the future (maybe 3-4 months).

@JMTyler
Copy link
Author

JMTyler commented Sep 10, 2013

Hey, thanks for the heads up! All the more reason for me to scrounge up some time in the near future to contribute ;-)

@lefnire
Copy link
Contributor

lefnire commented Sep 10, 2013

Yes please! :)

@goldbattle goldbattle added the bug label May 5, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants