GUI sometimes freezes

[humdinger]

This is hrev50837.

Sometimes when entering a search term right after launching HaikuDepot, it pegs one CPU for a long time (15s or longer) while becoming unresponsive.

Looks like it's nicely reproducible:

• open HaikuDepot and search for "editor"
• open Repository prefs and add/activate (or deactivate) a large repo, like Michel's at ​http://clasquin-johnson.co.za/michel/repo
• do "Refresh repositories" in HaikuDepot

The HaikuDepot GUI should be responsive at all times. An indicator of some sort should show that something's happening in the background. Even better: whatever it's doing, make it faster... :)

[humdinger]

(In #13245) > Isn't the menu to filter by repository in HaikuDepot simpler and faster than enabling and disabling repos in package management?

You're right. But to lessen the effects of #13244, I currently have Michel's mega repo deactivated. #13244 is actually a blocker for this ticket. No use to inflict more freezes on the user until that one is solved.

But if repo changes are instead made via pkgman nothing will happen. So another method would be for HaikuDepot to put a monitor on the repository cache.

Good call, I think this would be the right approach.

An important question though would be, is this automatic refreshing expected by the user, or would it be confusing?  Could it interrupt anything the user was doing (download/installing), reset current search parameters, do anything else that would make the user say "What are you doing, I was in the middle of doing X and now it changed on me!!!" ?

I thought about this and your example of "smart mail".
I think as long as the de/activating of repos is a result of the user's own action, it's completely save to update HaikuDepot's GUI. In fact, this is exactly what I expect and therefore wouldn't even go through the hassle of setting update-flags. HaikuDepot should always present the current state. It may have to learn to cancel a running update and start anew if it gets the message to update.

If I see something in HaikuDepot, I don't want it to fail when clicked on, but rather have it disappear when I just told via Repositories prefs to deactivate its repo. Currently, I get an error alert "failed to match for {packagename}".

One thing has to be made sure though: if it's not the currently selected item itself that's disappearing, the selection should be held and the position in the package list fixed, if possible.

All that said, de/activating repos and updating repos (in the background by the SoftwareUpdater to be) are rare enough occasions that I wouldn't mind an alert: "The repositories are about to be updated." "Thank you" (Or maybe even have the option not to update HaikuDepot's package list?)

[humdinger]

This has been fixed in the meantime. No more freezes, and HaikuDepot has a progress indicator now.

[nielx]

Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone