-
-
Notifications
You must be signed in to change notification settings - Fork 201
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
Chat opens again on stream restart #475
Comments
Which version of Chatty are you using? As I've described in #240, the Twitch GUI does not keep track of already running chat applications, because it's not possible to implement something that understands the various behaviors of each program (eg. single instance modes). The restart function is something different here though and chat programs should never be launched again when restarting a stream. |
Thanks for the answer. I had to mention that I am using Chatty 0.8.6 standalone (cause I dont want to install java just for one small program), and cause Twitch GUI expects chatty.jar in chatty folder I am forced to launch Chatty as a custom application like that: "D:\Programs\Chatty\Chatty.exe -connect -token "{token}" -channel "{channel}"". So for now I just added -single parameter and this totally suits me so I think you can close this. Maybe you could add Chatty.exe support at least? |
The chat application preset list is using an older implementation and needs a rewrite first. I have mention this in #410 (comment). I'll see if I can add a "Chatty standalone" profile, similar to the "Livestreamer standalone" streaming provider profile, once I have completed the rewrite. |
I'll add also a little request for the Tc chat preset then. |
Description
When I press "restart" this program opens new Chatty window and I need to close it everytime.
Environment details (operating system, etc.)
Windows 10
Comments, logs, screenshots, etc.
I suggest to not open chat window again if there is already one, or add an option to automatically close chat on stream restart/close so this will fix this issue aswell.
The text was updated successfully, but these errors were encountered: