Repository navigation
Conversation
|
it seems more logical to have the default click be the action that the user most wants to execute for me, i usually want the normal fetch with default settings. so an extra ctrl or extra ok click seems like extra work compared to other git clients Which do you most often use? the shortcuts or the ctrl + click? or do you always go through the options menu? |
|
I personally would settle with a reverse behaviour of the CTRL key. Means single click runs without confirmation and a CTRL does. Because I'm that sourcegit user who always hold CTRL everytime Push and Pull
|

Run Fetch / Pull / Push with one click, with optional saved defaults
simplify-fetch-pull-and-push-buttons.webm
Motivation
Most people don't change the options for fetch, pull, push very often. then set them once, then leave them be.
Currently the app always requires 2 clicks to fetch, pull, push. this change reduces that to 1 click, while also allowing the settings to be modified or one off runs with different settings.
What changed
Toolbar
Options panel
Behaviour changes
Implementation notes
Popuphas new virtual methods:HasDefaultOptions,SaveOptionsAsDefault()andResetDefaultOptions(). They are implemented byFetch,PullandPush.RepositoryUIStateshas three new fields:DealWithLocalChangesOnPull,SetTrackingOnPushandNoVerifyOnPush. The existingCheckSubmodulesOnPushis now actually used.Repository.RunPopupInBackgroundAsyncruns a popup'sSure()without showing the popup. It exposes theIsFetching/IsPulling/IsPushingandIs*Succeededstate that the toolbar binds to.Icons.ResetDefaultsicon.en_USonly:Text.Popup.SaveAsDefault,Text.Popup.ResetDefaults,Text.Repository.ShowOptions.