-
Notifications
You must be signed in to change notification settings - Fork 21
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
Add flatpak Discord Rich Presence support #39
Conversation
Started test build 3240 |
Build 3240 successful
|
Thank you for taking the time to do this. Could you elaborate a bit on what this feature does and how to test it? The discord website describes it as a source of viral advertising for games, is it intended to show other people on discord that you are playing games on dolphin? Does it do anything else? |
Yes, it allows to show other people what game you are playing on dolphin. Upstream dolphin already has this feature, this pull request only adds support for discord installed as a flatpak. See flathub/com.discordapp.Discord#29 and https://github.com/flathub/com.discordapp.Discord/wiki/Rich-Precense-(discord-rpc) for more informations. I tested both a local build and the build provided by the bot, and it appears to be working. To test it yourself you should install discord from flathub, create an account if you don't already have one, and then run dolphin. If you just created a new account probably the easiest way to test is to create a new server (green + on the left side of the window, you only have to provide a name). |
Desktop file needs updated. |
Queued test build for org.DolphinEmu.dolphin-emu. |
Started test build 3296 |
Build 3296 failed |
Started test build 3350 |
Build 3350 failed |
Started test build 3488 |
Build 3488 failed |
@Parnassius your builds are failing because of the new flathub appdata requirements, I've been meaning to fix it for a while but I haven't gotten around to doing it yet. |
bot, build |
Queued test build for org.DolphinEmu.dolphin-emu. |
Started test build 3502 |
Build 3502 failed |
Looks fine. @cpba can fix the appdata then we'll rebase this. |
I'm pretty sure I fixed it yesterday before bed, you can rebase.
…On Fri, 17 May 2019, 09:57 Patrick, ***@***.***> wrote:
Looks fine. @cpba <https://github.com/cpba> can fix the appdata then
we'll rebase this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#39?email_source=notifications&email_token=ACZPHZGZSPHI3NVMO6OTU3LPVZQONA5CNFSM4HMGGW72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVUBIRA#issuecomment-493360196>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACZPHZG3W3QA5UDSLL2DZHLPVZQONANCNFSM4HMGGW7Q>
.
|
Before this is merged, I hope to change discord-rpc socket path from |
Started test build 3776 |
Build 3776 successful
|
I understand that this pull request is waiting on flathub/com.discordapp.Discord#68 before it can be merged? |
The change required after that PR would be trivial, so it's probably not a blocker. Just be aware of its state. |
My concern is that if I merge this now, anybody who starts using it will
see it break when they update discord.
Would this be the case?
…On Wed, 22 May 2019, 00:31 Filippe LeMarchand, ***@***.***> wrote:
The change required after that PR would be trivial, so it's probably not a
blocker. Just be aware of its state.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#39?email_source=notifications&email_token=ACZPHZAAJR3S4LA6UHMYZA3PWRZ37A5CNFSM4HMGGW72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV5L27I#issuecomment-494583165>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACZPHZE23OEDIC3LNA3BUNTPWRZ37ANCNFSM4HMGGW7Q>
.
|
Yes.
|
Merged the Discord change so we can update this. |
Started test build 4045 |
Build 4045 successful
|
This has a merge conflict and needs to be rebased (feel free to squash). |
Started test build 4052 |
Build 4052 successful
|
Started test build 4053 |
Build 4053 successful
|
Should be ready now |
No description provided.