| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Definitely by pressing Ctrl-L but probably any of these would cause all
sorts of badness.
|
|
Also changed focus main/queue listings to [ and ], so that we can use
the 2 key for the down arrow on a number pad.
|
|
Otherwise you could type, for example, P to select "process...", then
close the menu, then reopen it and press R to jump to "remove...", but
it would just select "process" again because that matches "PR".
|
|
|
|
Actually it wasn't being updated at all. We need to pass an element to
selectInput, not an index!
|
|
Sorry :P
|
|
|
|
Previously (on Avatar), removing tracks from the queue would cause
a crash if the queue listing was scrolled down. This update fixes that.
|
|
|
|
Should think about moving this into tui-lib! It'd fit the boilerplate
function I have there already (I think), but we're not making use of
that in mtui yet.
|
|
|
|
|
|
|
|
I still prefer recordStore as the cleaner solution, but we were just
doing recordStore.app a lot of the time, and this really wasn't any
better than just passing app.
|
|
Fixes play/mark/etc status not updating right away.
|
|
|
|
|
|
|
|
|
|
..so that your scrollback isn't messed up by mtui's output when you
quit.
|
|
"v" increases because it's lowercase and therefore more likely to be
accidentally pressed, hence more likely to confuse the user when it
decreases the volume (if it decreased the volume - since it increases
the volume, it generally doesn't seem to have any effect until you've
already discovered that v and V are used for volume controls).
|
|
|
|
|
|
Items in the queue now have a menu, and if you pick "play later" from it
(the other option is "remove from queue"), it'll move that item into
somewhere further down in the queue. If it was already playing when you
select play later, it'll first skip it, then move it.
|
|
* Menus opened from the queue wouldn't work before. Now they do.
(Well, there's no code for them yet, but there was when I was
testing.)
* Rebuilding the items of a listing while it's selected doesn't reset
the selection (i.e. select AppElement -> Tabber -> left pane). So you
can remove an item from the queue and have focus remain on the queue,
at the index where the item you removed was.
|
|
|
|
|
|
AKA, prevent left/right from bubbling (I already intended this to happen
but I forgot a required return false).
|
|
|
|
|
|
If you press enter in the JumpElement form while it's still empty,
automatically treat the previously-entered input as the entered value,
so that it's easy to quickly do a "repeated" search (you don't have to
enter the same value over and over again).
|
|
Well, not the current index; rather the index which was selected when
the jump element was opened.
|
|
Previously the cursor would only follow the selected track if it was
selected by shift-up/down; now it works if it's automatically played
(i.e. by the previous song finishing).
|
|
Click to switch tab, scroll over the tab list to quickly switch to the
previous or next tab.
|
|
|
|
|
|
Basically, support for cors-anywhere.
(Cherry-picked from web-mtui branch)
|
|
|
|
|
|
|
|
Somebody remind me to write unit tests...
|
|
This was already half-done, but the new behavior in this commit feels
quite a bit nicer. (Specifically if you use shift-up/down (or n/p) while
the queue is selected, the cursor will move to the new selection if it
was already on the old selection, whereas before it would never follow
when the queue was selected.)
|
|
|
|
This also makes it so that the selected options in whereControl and
orderControl stay the same when you open the context menu on a different
item, browse a different group, etc.
|
|
E.g. to interweave two groups together.
|
|
|
|
This should be more intuitive and useful...most of the time. :)
|
|
Cool! This was one of my favorite tiny features of http-music.
|
