-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Split up the pull/fetch/rebase/merge button into separate buttons #3923
Comments
I suggest this feature to be implemented as optional / configurable When the dropdown is replaced by 4 (or 5) separate buttons, then whenever user fetches, I find the current look and behavior convenient, because I don't use fetch options others than the one selected as default. I also think this is true for many people, there is even a feature request #4159 which depends on current behavior. |
I agree that the metaphor for selecting the default option is somewhat odd. This would be much better expressed with a Ribbon, if we had one. However I also agree with @NikolayXHD that having several similarly looking buttons in the toolbar would have a high degree of probability of creating confusion. Whilst I appreciate that the current UX is somewhat imperfect and it may cause some discomfort to some of our users, I am not entirely convinced the proposal would makes it universally better for everyone. |
I have never been 100% happy with the split button. The idea I had to fix that, but never have had enough motivation to do it, is to make it configurable which button is the default button, which buttons should go next to the default button in the tool bar. The other buttons should go to drop down menu as it is now. All that configurations should take place in the settings dialog that we could remove the odd menu item to set the default action. |
We could also replace "Set the next selection as the default" checkbox with "Pull menu configuration" button that would lead to the corresponding settings page |
I'm happy for this discussion to be revisited when we ship v3 |
I think the best of both worlds would be to make the options inside the drop-down drag-able to the toolbar. |
But I let you imagine the difficulty and the effort to do such a thing! We are waiting your PR 😁 |
I like the way it is in the current v3.2.1 build with the options broken out on the drop down. Very useful and a great incremental improvement over v2.x |
* One for fetch operations, * One for rebase operations, * One for the more generic "pull dialog" The first two with there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, * One for the more generic "pull dialog" The first two with there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, * One for the more generic "pull dialog" The first two with there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, * One for the more generic "pull dialog" The first two with there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, * One for the more generic "pull dialog" The first two with there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, * One for the more generic "pull dialog" The first two with there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, * One for the more generic "pull dialog" The first two with there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, * One for the more generic "pull dialog" The first two with there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, * One for the more generic "pull dialog" The first two with there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, * One for the more generic "pull dialog" The first two with there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923
Voting to close this, no one is working on this. Also, as @gregsohl has mentioned (me included) the setup is quite nice now, if someone still has an issue, should open a new ticket/create a PR with suggested improvements, |
We have made a number of improvements in this area. There are no plans to split the buttons. |
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923 # Conflicts: # GitUI/CommandsDialogs/FormBrowse.Designer.cs # GitUI/CommandsDialogs/FormBrowse.cs
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923 # Conflicts: # GitUI/CommandsDialogs/FormBrowse.Designer.cs # GitUI/CommandsDialogs/FormBrowse.cs
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923 # Conflicts: # GitUI/CommandsDialogs/FormBrowse.Designer.cs # GitUI/CommandsDialogs/FormBrowse.cs
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923 # Conflicts: # GitUI/CommandsDialogs/FormBrowse.Designer.cs # GitUI/CommandsDialogs/FormBrowse.cs
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923
* One for fetch operations, * One for rebase operations, With there own default operation setting. Improvement over gitextensions#3923
Do you want to request a feature or report a bug?
Feature.
What is the current behavior?
All fetching and merging from the toolbar has to be done through a fiddly split button that requires an unnecessarily high degree of dexterity for succeess.
What is the expected behavior?
Remove the split button, together with the unintuitive and highly idiosyncratic "Set the next selection as the default" option. Introduce separate buttons for Merge, Rebase, Fetch, Fetch All and Open Pull Dialog.
Motivation
The vast majority of developers have high resolution monitors. We have plenty of empty space on the toolbar for more buttons. Pulling/merging/fetching is one of the most common operations. But we are currently forced to target a ~10 pixel-wide dropdown arrow to access the "non-default" actions.
This is made even more frustrating by the context menu's dismissal on mouse-out. It's too easy to slip off the edge and have to fiddle with the button again.
Lastly, the idea of setting the default action of a button from a menu on the button itself seems to be a completely random interaction, the likes of which I've only ever seen in GitExtensions.
All these issues are solved by breaking this weird and frustrating split button into regular top-level buttons.
The text was updated successfully, but these errors were encountered: