Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unblocking UI #53

Open
tigrawap opened this issue Feb 25, 2018 · 0 comments
Open

Unblocking UI #53

tigrawap opened this issue Feb 25, 2018 · 0 comments

Comments

@tigrawap
Copy link
Owner

tigrawap commented Feb 25, 2018

Right now search,filters, etc might block interface if nothing is found within reasonable time

Which is not big issue with small files(i.e <~100mb) but not so fun when making a typo in multi-GB file

General idea for solving the problem:

  • every action should have own cancellable context, every function called from event loop should expect (and best effort to respect) context
  • EventPoll overlay, which will gather all events and process one by one. In case some action already being processed - allow to flush all pending events(by throwing out keys, doing zero-job on interrupt requests(so interrupt-callers will be released)) when control sequence received (probably ctrl+c)
  • Add "Searching...press ctrl+c to stop" to infobar during explicit search/filter and implicit search/filter(i.e page down, which may cause additional big scan (i.e one page of HITs page down that leads to 1GB of misses). Implicit-search notice should appear with delay, to avoid flash-ing
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant