Handle idle time between fetch results #211

New Issue

wojtek · 2024-09-01T17:30:24+02:00

wojtek commented

2024-09-01 17:30:24 +02:00

It's a convenience but it will solve what is arguably a big problem. After hitting enter on a match there is no visual confirmation. If the next result is not ready yet the screen looks frozen and may prompt another enter hit. This enter will be queued up and immediately apply to the next match.

To solve this:

Switch from channel::recv to channel::try_recv.
If the result is not erase the matches screen and display a waiting message.
All key presses should be ignored except for the usual ones to abort.

It's a convenience but it will solve what is arguably a big problem. After hitting enter on a match there is no visual confirmation. If the next result is not ready yet the screen looks frozen and may prompt another enter hit. This enter will be queued up and immediately apply to the next match. To solve this: 1. Switch from channel::recv to channel::try_recv. 2. If the result is not erase the matches screen and display a waiting message. 3. All key presses should be ignored except for the usual ones to abort.

wojtek added this to the v1.0.0-alpha milestone 2024-09-01 17:30:24 +02:00

wojtek added the

enhancement

label 2024-09-01 17:30:24 +02:00

wojtek added this to the Album tracking project 2024-09-01 17:30:24 +02:00

wojtek changed title from ~~Add a fetch state to handle idle time between fetch results~~ to Handle idle time between fetch results

2024-09-01 17:50:56 +02:00

wojtek added reference 211---handle-idle-time-between-fetch-results

2024-09-01 21:14:35 +02:00

wojtek referenced a pull request that will close this issue

2024-09-01 22:48:36 +02:00

Handle idle time between fetch results #212