dir size is gone...

[Andrew Gaydenko]

Hi! For the current trunk state hitting space on dir doesn't result in dir size calculating. Is it a bug or feature? :) Probably we must use another way to calculate dir size now...

[A. Bikadorov]

Yes, I removed it. See https://phabricator.kde.org/D4747 .

Instead, you can simply assign a shortcut (e.g CTRL+SPACE) to the "Calculate occupied
space" action and use it the same way.

Cheers
Alex

[Andrew Gaydenko]

He-he... How standard our brains are... I have already assigned exactly that combination! :)

On the other hand I would vote to keep old behavior also: to quickly estimate space distribution between ten subdirs inside a dir with plenty of subdirs I'm forced to close information dialog ten times.

The second argument is the culture :) I mean decades of similar behavior of plenty of file managers (including Krusader). So, it isn't just very expected behavior, it has grown up to the level of culture, I guess...

[A. Bikadorov]

On 01.03.2017 19:07, Andrew Gaydenko wrote:
> On the other hand I would vote to keep old behavior also: to quickly estimate space
> distribution between ten subdirs inside a dir with plenty of subdirs I'm forced to close
> information dialog ten times.

You can simply select all ten dirs and hit "CTRL+SPACE". As an advantage the calculation
is not blocking anymore and you can use Krusader while the calculation is done.

> The second argument is the culture :) I mean decades of similar behavior of plenty of file
> managers (including Krusader). So, it isn't just very expected behavior, it has grown up
> to the level of culture, I guess...

The problem was, it didn't fit anymore because the calculation is not blocking the
application input. Before, you could press and hold the space key with maybe some flashing
(and more or less useless) dialogs until all dirs are done. Now, multiple dialogs will be
opened and closed - even worse.

I can start working on a replacement:
Space key will start calculation in background (without dialog but maybe a progress bar)
for the current dir. Or if there already is a background calculation the current dir will
be added.

But it would require some time, so only if you really need this.

Cheers
Alex

[Andrew Gaydenko]

Alex, thanks for the tip with preliminary multiple selection. In fact this way resolves my issue. So, as far as there are still no crowd of angry Krusader users demanding to return old behavior, I guess, it can be kept as is (that is the way you have it all already done). Thanks!

I think a little polishing can be added: an opportunity to close information dialog with SPACE (that is to make OK button focused).

[A. Bikadorov]

On 01.03.2017 20:03, Andrew Gaydenko wrote:
> I think a little polishing can be added: an opportunity to close information dialog
> with SPACE (that is to make OK button focused).

Done. It was already "default", now its focused.

Cheers
Alex

[Andrew Gaydenko]

Got it, great. thanks!

[bernd.bu...@googlemail.com]

Am Mittwoch, 1. März 2017 19:53:33 UTC+1 schrieb A. Bikadorov:

On 01.03.2017 19:07, Andrew Gaydenko wrote:

> On the other hand I would vote to keep old behavior ...

You can simply select all ten dirs and hit "CTRL+SPACE". As an advantage the calculation
is not blocking anymore and you can use Krusader while the calculation is done.

I can start working on a replacement:
Space key will start calculation in background (without dialog but maybe a progress bar)
for the current dir. Or if there already is a background calculation the current dir will
be added.

But it would require some time, so only if you really need this.

Today, I updated from 2.4 beta 3 to 2.6.0 and missing the feature discussed here, I tried the proposal. Well, no one is dying but I really miss the old behaviour - what I do very often is selecting folder by folder with space to find the one I think to be the culprit of occupying too much space.

Anyway, why do we have to show a pop up and confirm it when the size of the calculated directory is shown in the list?

But as I said, no one, including me is dying because of this ...

 

[A. Bikadorov]

This feature was already re-added (with commit c447f1813f2) but no new release is
published yet.

I hope I can manage a new release around christmas.

Cheers
Alex

[bernd.bu...@googlemail.com]

Am Sonntag, 12. November 2017 18:06:15 UTC+1 schrieb A. Bikadorov:

This feature was already re-added (with commit c447f1813f2) but no new release is
published yet.

In between, I installed a git version and the discussed feature works with this to my perfect satisfaction. Thanks very much.