You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be possible to add an option to keep the /resources/Scrcpy version up to date with the Genymobile repo? This could be implemented in two ways:
As an option in the GUI, along with automatic updates to Scrcpy+, to automatically fetch the latest release from the Genymobile repo and unpack it in the /resources/scrcpy directory.
As a separate release channel for Scrcpy+, e.g. named Scrcpy+alpha. It would be a separate branch in this scrcpy-plus github repo containing a workflow Action (I believe I could help do a PR for this if needed) that would automatically merge this repo's /resources/scrcpy folder with the latest upstream from Genymobile and publish a new release. Users who choose to install Scrcpy+alpha would get automatic updates from this channel instead of the regular release channel.
Either way, users would have the option to get the latest improvements from Genymobile/scrcpy immediately, without waiting for this repo to be updated manually. Users would be warned that since you, the Scrcpy+ dev, have not had a chance to test out the latest changes for compatibility and publish an official Scrcpy+ update, some features may break as a result of upstream changes.
The text was updated successfully, but these errors were encountered:
Would it be possible to add an option to keep the
/resources/Scrcpy
version up to date with the Genymobile repo? This could be implemented in two ways:/resources/scrcpy
directory./resources/scrcpy
folder with the latest upstream from Genymobile and publish a new release. Users who choose to install Scrcpy+alpha would get automatic updates from this channel instead of the regular release channel.Either way, users would have the option to get the latest improvements from Genymobile/scrcpy immediately, without waiting for this repo to be updated manually. Users would be warned that since you, the Scrcpy+ dev, have not had a chance to test out the latest changes for compatibility and publish an official Scrcpy+ update, some features may break as a result of upstream changes.
The text was updated successfully, but these errors were encountered: