Replies: 2 comments
-
System for doing something similar already exists, just not in the GUI. You can create .syncplay configuration files in any media folders you have and they will apply custom settings (like sever address) whenever you open Syncplay with a file from said folder or one further down in hierarchy. Basically like .htaccess works for Apache. We never really got around to adding it to GUI for 2 reasons:
That said, with some discussion about how exactly it should look like and function - this could be a feature worth thinking about if somebody is up for implementing it. |
Beta Was this translation helpful? Give feedback.
-
This is a feature which was requested in #371 back in December 2020. My response from the time is still relevant and formed the basis for what I put on https://syncplay.pl/guide/trouble/ in response to the question "I use multiple servers. How do I remember different settings for each server?". That original response was as follows: When it comes to profiles, different people might want different things to change. As such, there is no one simple profile system which would satisfy everyone. Adding additional UI elements might make it easier for some, but it could make it more confusing for others. For Windows users there are three main ways to do a profile system that already work with the current version of Syncplay, and some work for other operating systems (some requiring appropriate tweaks): I think for 99% of use cases, option (1) is perfectly fine, and for the rest (2) is perfectly adequate. If you give me a common use case where it isn't enough then that could potentially justify an additional command line option such as --config-path=[] to allow for people to specify multiple profiles. This would help keep the interface clean, allowing more advanced users to specify multiple profiles without it cluttering or confusing things for regular users. |
Beta Was this translation helpful? Give feedback.
-
It would be very nice to store a variety of Connection settings, like in Mumble, that can each be accessed with a single click.
In my opinion those connection profiles should store both, server and room, maybe listed as Room@Server.
Beta Was this translation helpful? Give feedback.
All reactions