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
Currently, server switching (silent or user-initiated) results in sending a deactivate signal to the platform-specific controller, followed by an activate signal. However, for all platforms (except possibly flatpaks), the deactivate is a no-op. This is confusing, and has tripped up many people interpreting this code. Additionally, using the activate signal for a config switch (to a new tunnel) is responsible for an entire class of bugs.
We should add a new controller function for server switches, streamlining this code.
┆Issue is synchronized with this Jira Task
┆Reporter: Matt Cleinman
The text was updated successfully, but these errors were encountered:
Currently, server switching (silent or user-initiated) results in sending a deactivate signal to the platform-specific controller, followed by an activate signal. However, for all platforms (except possibly flatpaks), the deactivate is a no-op. This is confusing, and has tripped up many people interpreting this code. Additionally, using the activate signal for a config switch (to a new tunnel) is responsible for an entire class of bugs.
We should add a new controller function for server switches, streamlining this code.
┆Issue is synchronized with this Jira Task
┆Reporter: Matt Cleinman
The text was updated successfully, but these errors were encountered: