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

[Feature request] Sorting the results by state/name #598

Closed
lisandrocarmona opened this Issue Nov 9, 2016 · 2 comments

Comments

2 participants
@lisandrocarmona

lisandrocarmona commented Nov 9, 2016

I'm not being able to find which databases are failing to be compressed. There are tons of them (all green) and can't find 2 of them that can't be managed by SDMaid. Maybe a sort option by state/name into the results list (or even in the options) will make it easy for us to make exclusions.

@d4rken d4rken added the c: Databases label Nov 9, 2016

@d4rken d4rken added this to the Next Tasks milestone Nov 9, 2016

@d4rken

This comment has been minimized.

Owner

d4rken commented Nov 9, 2016

Why would you prefer to exclude the failed entries, assuming no side-effects, ignoring them would also work, most failures due to schema issues fail early on not resulting in a process slowdown.

The current sortmode is database size, when would name sort be interesting and would it be appname, packagename or even filename?

@lisandrocarmona

This comment has been minimized.

lisandrocarmona commented Nov 9, 2016

I agree that this particular exclusion is not absolutely necessary. Just that when running the app I can see that everything went ok and, from time to time, which new installed app is falling due to schema issues.

Sorting by state: compressed ok (green) and failed to compress (red).
Sorting by name is less important in my opinion, but I think it'll be easy for users to see appname (less people know packagename and filename android schemes).

@d4rken d4rken added the enhancement label Nov 9, 2016

@d4rken d4rken modified the milestones: v4.5.0, Next Tasks Dec 9, 2016

@d4rken d4rken closed this Dec 10, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment