-
Notifications
You must be signed in to change notification settings - Fork 117
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
#SteamUI_JoinDialog_LaunchGameReady #493
Comments
I’m fairly sure DirtDiglett is no longer fixing this skin. As steam changes more things, themes will get progressively more broken. Even though I like pressure way better than the normal theme, I’ve finally given up on it. I have seen some forks which fixed an issue here and there but that’s about it. I remember reading diglett saying that steam considers theming dead, but I can’t find it anymore, so don’t quote me on that. |
Hi,
So when was the last fix? Cause i remember the previous issue that broke pressure and it was why pressure 2 was created i think. But the it was fixed...
I like both skins, but i don't like the white pressure 2 skin. I prefer and am used to dark skins.
Get Outlook for Android<https://aka.ms/ghei36>
…________________________________
From: TheDoctor40 <[email protected]>
Sent: Wednesday, October 2, 2019 4:31:37 AM
To: DirtDiglett/Pressure-for-Steam <[email protected]>
Cc: Victoria Johnston <[email protected]>; Author <[email protected]>
Subject: Re: [DirtDiglett/Pressure-for-Steam] #SteamUI_JoinDialog_LaunchGameReady (#493)
[EXTERNAL EMAIL]
I’m fairly sure DirtDiglett is no longer fixing this skin. As steam changes more things, themes will get progressively more broken. Even though I like pressure way better than the normal theme, I’ve finally given up on it. I have seen some forks which fixed an issue here and there but that’s about it.
I remember reading diglett saying that steam considers theming dead, but I can’t find it anymore, so don’t quote me on that.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#493?email_source=notifications&email_token=AEMTUELLUPLAVQQLAGDOZM3QMRL6TA5CNFSM4I4QYW52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAD7OHI#issuecomment-537392925>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AEMTUEPMWYNIKJ46WUTRP7DQMRL6TANCNFSM4I4QYW5Q>.
|
The last release was July 2017, the last modification to the source code was “last year” in the beta branch according to github. Master is even older. |
Is that even an issue with the skin? Looks to me like the strings just haven't loaded which has nothing to do with the skin. Even if it is a bug, this skin isn't going to get updated. I don't even remember how Steam skinning works anymore and as far as bugs go, this is a pretty minor one - assuming this is an issue with the skin (I don't know). |
I was not sure what it was. Which is why i posted it.
Get Outlook for Android<https://aka.ms/ghei36>
…________________________________
From: Js41637 <[email protected]>
Sent: Wednesday, October 2, 2019 6:04:27 AM
To: DirtDiglett/Pressure-for-Steam <[email protected]>
Cc: Victoria Johnston <[email protected]>; Author <[email protected]>
Subject: Re: [DirtDiglett/Pressure-for-Steam] #SteamUI_JoinDialog_LaunchGameReady (#493)
[EXTERNAL EMAIL]
Is that even an issue with the skin? Looks to me like the strings just haven't loaded which has nothing to do with the skin.
Even if it is a bug, this skin isn't going to get updated. I don't even remember how Steam skinning works anymore and as far as bugs go, this is a pretty minor one - assuming this is an issue with the skin (I don't know).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#493?email_source=notifications&email_token=AEMTUEO7TIV3VVJDNV74Z5DQMRW2XA5CNFSM4I4QYW52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAEHPFQ#issuecomment-537425814>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AEMTUELSRJZWH2ZHJRAWINDQMRW2XANCNFSM4I4QYW5Q>.
|
Seen the above once, hoping it will never be seen again. Posting just in case it's not just me that's seen this.
The text was updated successfully, but these errors were encountered: