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
While doing the diagnostics, it would be good to be able to link to specific preference panes (and ideally even specific preference items) so that we can more easily let the user fix things.
Proposed Solution
Something like a x-rd-preferences:// protocol handler, or somehow handle it in app://, or anything of the sort.
Additional Information
This seems better than changing the preference immediately, which wouldn't let the user know what happened.
The text was updated successfully, but these errors were encountered:
Something like a x-rd-preferences:// protocol handler, or somehow handle it in app://, or anything of the sort.
I think doing this in-app would be preferable; otherwise we have to create custom protocol handlers for all platforms.
Additional Information
This seems better than changing the preference immediately, which wouldn't let the user know what happened.
I think it depends. When the fix action is "Add ~/.rd/bin to the end of the PATH", then I think we should just do it for the user. The diagnostic needs to be verbose enough to mention the current setting, and the new setting it would change to.
I would be diagnostics like "You allocated 100% of the CPUs to Rancher Desktop; reduce the allocation to leave something for the OS and other applications" that would require the user to make a choice.
Problem Description
While doing the diagnostics, it would be good to be able to link to specific preference panes (and ideally even specific preference items) so that we can more easily let the user fix things.
Proposed Solution
Something like a
x-rd-preferences://
protocol handler, or somehow handle it inapp://
, or anything of the sort.Additional Information
This seems better than changing the preference immediately, which wouldn't let the user know what happened.
The text was updated successfully, but these errors were encountered: