summaryrefslogtreecommitdiffstats
path: root/src/interactive/widgets/mark.rs
AgeCommit message (Collapse)Author
2019-06-15pane is now displayed during deletion; keeps last item selectedSebastian Thiel
2019-06-15better separation of concerns when iterating marked itemsSebastian Thiel
also: fix consumption of mark-pane - it's now not always consuming it.
2019-06-15First half-baked version of deletion within traversal treeSebastian Thiel
No size handling for now
2019-06-15refactorSebastian Thiel
2019-06-15refactorSebastian Thiel
2019-06-15First rough version of the required pieces in MarkPaneSebastian Thiel
2019-06-14first sketch of the delete-draw-loopSebastian Thiel
2019-06-08Dehli/India: Make marker selection feel rightSebastian Thiel
2019-06-08Pune/India: Nicer colors for warn window in selectionSebastian Thiel
2019-06-08Pune/India: Warning window follows user selectionSebastian Thiel
2019-06-08Pune/India: Fix handling of deleting the first index in the mark listSebastian Thiel
2019-06-08Pune/India: more prominent selection in mark paneSebastian Thiel
2019-06-08Pune/India: Rustic way of handling the mark panes disappearanceSebastian Thiel
Interesting: before that fix, the GUI was in an invalid state, as the mark pane disappeared without setting the focus back to the main window. Thanks to everything being encoded in the typesystem and no assumptions made, the program wouldn't crash when buttons are pressed, which would otherwise be attempted to dispatch to the now gone mark pane. Instead one could press 'q' or tab, as fortunately, the pane handling is always done before any of the panes get a chance.
2019-06-08Pune/India: don't show warning if nothing is marked anymoreSebastian Thiel
this can happen if the user removes all entries. The pane stays open in this case, which is a little inconsistent, but not worth fixing as it's certainly not the common case. If it should be fixed, the 'key()' function should become consuming to possible delete the pane.
2019-06-08Pune/India: Actually hook up spacebar in mark paneSebastian Thiel
2019-06-08Pune/India: Better handling of what is selected after removing a marked entrySebastian Thiel
2019-06-08Pune/India: Don't try to go down as marked items are removedSebastian Thiel
2019-06-07First version of removing marked items from the listSebastian Thiel
2019-06-07Only show hotkey for deletion when focus is on the mark paneSebastian Thiel
2019-06-07First version of help line which tells what to do to delete thingsSebastian Thiel
2019-06-07Grapheme handling when truncating long filenamesSebastian Thiel
2019-06-07First prettier version of mark paneSebastian Thiel
2019-06-07Proper scrolling in mark paneSebastian Thiel
If something is selected, it behaves like you expect. Otherwise, it always shows the bottom of the list.
2019-06-07Happy clippySathish
2019-06-07refactorSebastian Thiel
2019-06-07move EntryMarkMap into Mark widgetSebastian Thiel
2019-06-07moved marked information from footer to title of mark paneSebastian Thiel
2019-06-07maintain sorting even though we have a map - each render must allocate nowSebastian Thiel
Maybe it's better to just spend the time searching through an array, which we could sort before and do a bisection. ... sounds better actually. Even though... that might even be more expensive if the sorting is done every time. Just stick to a list, huh?
2019-06-07see how it is when sorting by alphabetSebastian Thiel
It's what yuou want when deleting things, but not when displaying them.
2019-06-06tests to verify focus handling worksSebastian Thiel
2019-06-06implement actual marker selectionSebastian Thiel
2019-06-06Know about focus in marker paneSebastian Thiel
2019-06-06Simplify mark selection by making it based on position in listSebastian Thiel
And not on node index, which plays much less of a role there, if any
2019-06-06Move ownership of marked entries to the MarkPaneSebastian Thiel
interesting experience... it's easier to just keep state central, and have one place where mutation happens. Now that things are all over the place, it becomes more difficult to handle. However, I believe there is a way, the problem here is the hybrid state the program is currenlty in... partly centralized, partly localized.
2019-06-06some experimentation with selection handling in the new paneSebastian Thiel
It's entirely different from the first one :D, incredible
2019-06-06A step towards more self-contained componentsSebastian Thiel
2019-06-06reactor help: move event handling closer to where it belongsSebastian Thiel
2019-06-06refactorSebastian Thiel
2019-06-06The first display of paths to be deleted!Sebastian Thiel
Still no way to show that one is contained in others... probably not needed right now... .
2019-06-06The first incarnation of the mark windowSebastian Thiel