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

Ability to cancel an ongoing search #720

Open
opusforlife2 opened this issue Dec 12, 2019 · 7 comments
Open

Ability to cancel an ongoing search #720

opusforlife2 opened this issue Dec 12, 2019 · 7 comments
Labels
Feature Issues that introduce new functionality to the project, instead of updating existing functionality
Milestone

Comments

@opusforlife2
Copy link
Contributor

When the user searches for a package in a source tab, the GUI blocks the user from doing anything else (other than close ChocolateyGUI entirely).

The user should have the option to cancel the search.

Alternatively, the GUI should not block the user from interacting with the application, while the search is executed in the background.

@gep13 gep13 added the Feature Issues that introduce new functionality to the project, instead of updating existing functionality label Dec 12, 2019
@gep13 gep13 changed the title [Feature Request] Ability to cancel an ongoing search Ability to cancel an ongoing search Dec 12, 2019
@gep13
Copy link
Member

gep13 commented Dec 12, 2019

This issue was created after discussion in this issue: #595

@opusforlife2
Copy link
Contributor Author

Hey, since the 0.17 pre-release got the option to execute a search only upon pressing Enter, it has saved me a lot of headache. This partially addresses the issue, and should be the default setting for users, in my opinion.

@opusforlife2
Copy link
Contributor Author

Alternatively, the GUI should not block the user from interacting with the application, while the search is executed in the background.

Is this part complicated to fix? It's a giant terminal that blocks you from doing anything, but just has a useless "loading results" kind of message. The user should be free to interact with the UI while it loads the next page.

@gep13
Copy link
Member

gep13 commented Apr 5, 2020

@opusforlife2 said...
The user should be free to interact with the UI while it loads the next page.

Just so we are on the same page... What other interaction would you want to be taking while the results are being loaded?

@opusforlife2
Copy link
Contributor Author

  • Scrolling the page.
  • Opening Settings or About.
  • Changing the item view from list/grid to the other.
  • Going back to the installed list of apps.
  • Opening a different remote view (though I have only chocolatey right now).
  • Searching for a different term (which should automatically cancel the current loading process).
  • Loading the previous/next page without waiting for the current load to finish (this should also cancel current loading process).

(other than close ChocolateyGUI entirely)

I just realised even this isn't unblocked when loading a new page, only minimize and resize are unblocked.

@opusforlife2
Copy link
Contributor Author

I suppose the milestone needs to be bumped.

@pauby pauby modified the milestones: 0.20.0, Future Dec 23, 2021
@opusforlife2
Copy link
Contributor Author

Still needed as of 2.1.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Issues that introduce new functionality to the project, instead of updating existing functionality
Projects
None yet
Development

No branches or pull requests

3 participants