Age | Commit message (Collapse) | Author | |
---|---|---|---|
2020-02-25 | show item counts in frames | Jesse Duffield | |
2020-02-15 | remove old createMenu function | Jesse Duffield | |
2020-02-15 | continue refactor of menu panel | Jesse Duffield | |
2020-02-15 | begin refactor of menu panel | Jesse Duffield | |
2020-01-07 | fix display of menu option keybindings | David Chen | |
2019-11-21 | better handling of click events in list views | Jesse Duffield | |
2019-11-21 | extract out some logic for list views | Jesse Duffield | |
2019-11-21 | add contexts to views | Jesse Duffield | |
2019-11-10 | add mouse support | Jesse Duffield | |
2019-10-20 | Added light theme option to the settings | mjarkk | |
2019-06-08 | revert menu panel error panel usage | Jesse Duffield | |
2019-06-06 | allow stashing staged changes | Jesse Duffield | |
reinstate old stash functionality with the 's' keybinding | |||
2019-03-23 | delete menu keybinding before setting new one | Jesse Duffield | |
2019-03-23 | Rely on model rather than view to focus a point | Jesse Duffield | |
Currently when we want to focus a point on a view (i.e. highlight a line and ensure it's within the bounds of a view's box, we use the LinesHeight method on the view to work out how many lines in total there are. This is bad because for example if we come back from editing a file, the view will have no contents so LinesHeight == 0, but we might be trying to select line 10 because there are actual ten things we expect to be rendered already. This causes a crash when e.g. 10 is greater than the height of the view. So we need to pass in to our FocusPoint method the actual number of items we want to render, rather than having the method rely on the LinesHeight, so that the method knows to scroll a bit before setting the cursor's y position. Unfortunately this makes for some awkward code with our current setup. We don't have a good interface type on these state objects so we now need to explicitly obtain the len() of whatever array we're rendering. In the case of the menu panel this is even more awkward because the items list is just an interface{} and it's not easy to get the list of that, so now when we instantiate a menu we need to pass in the count of items as well. The better solution would be to define an interface with a getItems and getLength method and have all these item arrays become structs implementing the interface, but I am too lazy to do this right now :) | |||
2019-03-03 | allow both enter and space to execute menu itemv0.7 | Jesse Duffield | |
2019-02-16 | consider whether the view has focus when rendering the contents of a view | Jesse Duffield | |
2019-02-16 | introduce panel contexts and more work on rebasing | Jesse Duffield | |
2019-02-11 | Merge branch 'master' into feature/rebasing | Jesse Duffield | |
2019-01-17 | Directly send wrap argument rather than the view | Jesse Duffield | |
2018-12-11 | Make merge panel its own panel | Jesse Duffield | |
2018-12-08 | fetching branches without checking out | Jesse Duffield | |
2018-12-08 | standardising how list panels deal with cursor movement | Jesse Duffield | |
2018-09-18 | generalise popup menu panel | Jesse Duffield | |
2018-09-17 | minor refactor | Jesse Duffield | |
2018-09-17 | standardise rendering of lists in panels | Jesse Duffield | |
2018-09-12 | remove redundant comments | Jesse Duffield | |
2018-09-10 | better handling of cursor and origin positionings | Jesse Duffield | |
2018-09-07 | ladies and gentlemen... | Dawid Dziurla | |
this is fmt number x+1 | |||
2018-09-07 | rewrite some of menu panel logic | Dawid Dziurla | |
panel keybindings are now on top and global keybindings are below separated with empty newline | |||
2018-09-05 | include global keybindings in menu | Dawid Dziurla | |
2018-09-05 | help -> menu | Dawid Dziurla | |