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

Small bug in filemin #402

Closed
ChriZathens opened this issue Feb 19, 2016 · 5 comments
Closed

Small bug in filemin #402

ChriZathens opened this issue Feb 19, 2016 · 5 comments

Comments

@ChriZathens
Copy link

Hello!
I would like to report a small bug:
When in filemin, I select a folder by checking it (BTW I remember there was a setting to automatically calculate the size of the selected, but can't seem to find it now), I right click and select Properties ---> calculate selected size.
In the upper left corner it displays ...

Selected: 1 entries 400MB

Having left the previous folder checked, I repeat the process
In the upper left corner it displays ...

Selected: 2 entries 656MB

So far so good..
But now, If I uncheck any one of the two selected folders now I have

Selected: 1 entries

and no space reported.
If this is on purpose, due to any reason you have, then fine..
Just thought I should report it..
Thanks for your great theme!!!

@iliajie
Copy link
Collaborator

iliajie commented Feb 19, 2016

Thank you for your kind word.

This is exactly on purpose, as when selection happens, the size also should change.

@ChriZathens
Copy link
Author

OK, I see! Great then, thanks!

I also noticed another thing while fiddling around with those filemin selections
Clicking on "select all" button, in the upper left corner it does not realize that all is now selected and it displays

*Selected: 0 entries *

even after this , if I right click anywhere on the selected items and select Properties ---> calculate selected size it displays

Selected: 0 entries 880.73 GB
(It calculates the size, but still says 0 entries)

The above also happens with invert selection button

@iliajie
Copy link
Collaborator

iliajie commented Feb 19, 2016

Oh, that must be a bug.

Thanks for reporting, will fix, that.

@iliajie
Copy link
Collaborator

iliajie commented Feb 21, 2016

Great discovery, thanks for reporting. It will be fixed in 17.72

@iliajie iliajie closed this as completed Feb 21, 2016
@iliajie
Copy link
Collaborator

iliajie commented Feb 21, 2016

Please upgrade to 17.72.

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

2 participants