Closed TheOnlyArtz closed 5 years ago
hmm... That's weird, when I close Atom, there is not processes remaining.
Maybe this is provided by some kind of packages?
Okay, I'll add expire time when next commit.
I found out that adding endTimestamp only makes elapsed to left. I think the fundamental solution is tracking opened windows.
I have this same problem and it is still not working correctly and there is no background process on my pc and it is still going.
If there is no background process, it may bug of Discord. Because Discord detects process and only shows Rich Presence of running process
.
That's so weird I got some. Maybe external packages?
Is the issue have solved?
I added a code to destroy RPC Client properly.
Nice! It's solved
I can't find out the reason this error is occured.
According to Hallo89 (#24), there's a brief moment that Discord detects not playing. When I record log output, after destroying RPC Client, the Discord detects not playing and although neither packets are sent nor reopened RPC, Discord detects I am playing again.
Maybe removing inactivity packet help solving this issue.
That can be reasonable, can't you just destroy the client when Atom shuts down?
It also appears that sometimes this issue doesn't appear, but I can't see what exactly triggers it. I have some theses for this:
Now, I have no idea of programming beside html/css, so this might sound stupid, but I hope this helps anyway ^^
Sorry to make you get bad but HTML / CSS aren't programming languages, and if you think about it deeply, JavaScript isn't too, HTML is a markup language and JavaScript is a scripting language
... I am, indeed, aware of that by all means
Well... Looks like it fucks up even more now @HelloWorld017
What's different? That's exactly what this issue consists of
No, The issue was the rich presence was still on, now it's just the name
Yeah okay, but I pointed it out earlier :D see #24
it only shows this for me
Hey there! First of all, this is a super cool package for Atom But... There's a bug, We know that when we're closing Atom there's a background process that runs for Updates and Booting the software faster. Atom-Discord detects those and thinks I'm still inside Atom, so the RichPresence will never get off my profile