6 commits

Author	SHA1	Message	Date
Jesse Duffield	51fb82d6bf	Enforce single-item selection in various actions ... We want to show an error when the user tries to invoke an action that expects only a single item to be selected. We're using the GetDisabledReason field to enforce this (as well as DisabledReason on menu items). I've created a ListControllerTrait to store some shared convenience functions for this.	2024-01-19 10:50:49 +11:00
Jesse Duffield	54bd94ad24	Add SetSelection function for list contexts and use it in most places ... The only time we should call SetSelectedLineIdx is when we are happy for a select range to be retained which means things like moving the selected line index to top top/bottom or up/down a page as the user navigates. But in every other case we should now call SetSelection because that will set the selected index and cancel the range which is almost always what we want.	2024-01-19 10:47:21 +11:00
Jesse Duffield	24a4302c52	Add range selection ability on list contexts ... This adds range select ability in two ways: 1) Sticky: like what we already have with the staging view i.e. press v then use arrow keys 2) Non-sticky: where you just use shift+up/down to expand the range The state machine works like this: (no range, press 'v') -> sticky range (no range, press arrow) -> no range (no range, press shift+arrow) -> nonsticky range (sticky range, press 'v') -> no range (sticky range, press arrow) -> sticky range (sticky range, press shift+arrow) -> nonsticky range (nonsticky range, press 'v') -> no range (nonsticky range, press arrow) -> no range (nonsticky range, press shift+arrow) -> nonsticky range	2024-01-19 10:47:21 +11:00
Jesse Duffield	b838b74801	do not highlight line if there are no items to display	2022-04-16 15:19:32 +10:00
Jesse Duffield	d93fef4c61	use generics to DRY up context code	2022-03-19 12:12:57 +11:00
Jesse Duffield	c084abb378	move more view model logic into the files view model	2022-03-17 19:13:40 +11:00