Age | Commit message (Collapse) | Author | |
---|---|---|---|
2019-06-15 | pane is now displayed during deletion; keeps last item selected | Sebastian Thiel | |
2019-06-15 | better separation of concerns when iterating marked items | Sebastian Thiel | |
also: fix consumption of mark-pane - it's now not always consuming it. | |||
2019-06-15 | First half-baked version of deletion within traversal tree | Sebastian Thiel | |
No size handling for now | |||
2019-06-15 | refactor | Sebastian Thiel | |
2019-06-15 | refactor | Sebastian Thiel | |
2019-06-15 | First rough version of the required pieces in MarkPane | Sebastian Thiel | |
2019-06-14 | first sketch of the delete-draw-loop | Sebastian Thiel | |
2019-06-08 | Dehli/India: Make marker selection feel right | Sebastian Thiel | |
2019-06-08 | Pune/India: Nicer colors for warn window in selection | Sebastian Thiel | |
2019-06-08 | Pune/India: Warning window follows user selection | Sebastian Thiel | |
2019-06-08 | Pune/India: Fix handling of deleting the first index in the mark list | Sebastian Thiel | |
2019-06-08 | Pune/India: more prominent selection in mark pane | Sebastian Thiel | |
2019-06-08 | Pune/India: Rustic way of handling the mark panes disappearance | Sebastian 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-08 | Pune/India: don't show warning if nothing is marked anymore | Sebastian 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-08 | Pune/India: Actually hook up spacebar in mark pane | Sebastian Thiel | |
2019-06-08 | Pune/India: Better handling of what is selected after removing a marked entry | Sebastian Thiel | |
2019-06-08 | Pune/India: Don't try to go down as marked items are removed | Sebastian Thiel | |
2019-06-07 | First version of removing marked items from the list | Sebastian Thiel | |
2019-06-07 | Only show hotkey for deletion when focus is on the mark pane | Sebastian Thiel | |
2019-06-07 | First version of help line which tells what to do to delete things | Sebastian Thiel | |
2019-06-07 | Grapheme handling when truncating long filenames | Sebastian Thiel | |
2019-06-07 | First prettier version of mark pane | Sebastian Thiel | |
2019-06-07 | Proper scrolling in mark pane | Sebastian Thiel | |
If something is selected, it behaves like you expect. Otherwise, it always shows the bottom of the list. | |||
2019-06-07 | Happy clippy | Sathish | |
2019-06-07 | refactor | Sebastian Thiel | |
2019-06-07 | move EntryMarkMap into Mark widget | Sebastian Thiel | |
2019-06-07 | moved marked information from footer to title of mark pane | Sebastian Thiel | |
2019-06-07 | maintain sorting even though we have a map - each render must allocate now | Sebastian 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-07 | see how it is when sorting by alphabet | Sebastian Thiel | |
It's what yuou want when deleting things, but not when displaying them. | |||
2019-06-06 | tests to verify focus handling works | Sebastian Thiel | |
2019-06-06 | implement actual marker selection | Sebastian Thiel | |
2019-06-06 | Know about focus in marker pane | Sebastian Thiel | |
2019-06-06 | Simplify mark selection by making it based on position in list | Sebastian Thiel | |
And not on node index, which plays much less of a role there, if any | |||
2019-06-06 | Move ownership of marked entries to the MarkPane | Sebastian 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-06 | some experimentation with selection handling in the new pane | Sebastian Thiel | |
It's entirely different from the first one :D, incredible | |||
2019-06-06 | A step towards more self-contained components | Sebastian Thiel | |
2019-06-06 | reactor help: move event handling closer to where it belongs | Sebastian Thiel | |
2019-06-06 | refactor | Sebastian Thiel | |
2019-06-06 | The 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-06 | The first incarnation of the mark window | Sebastian Thiel | |