[dolphin] [Bug 422006] [Dolphin] Emptying trash does not trigger view refresh

[Pete]

https://bugs.kde.org/show_bug.cgi?id=422006

--- Comment #33 from Pete <pete at ozmartians.com> ---
(In reply to Méven Car from comment #32)
> (In reply to Pete from comment #31)
> > (In reply to Méven Car from comment #30)
> > > Which desktop layout are using desktop or folder view ?
> > > You have folder view if you have icons of your wallpaper/desktop.
> > > 
> > > Simply put, do you have icons on your desktop ?
> > > Does opening `desktop:/` in dolphin change the behavior ?
> > > 
> > > A component watching for trash updates, is not started if you use the
> > > "desktop" layout and might explain why I don't reproduce this.
> > > Haven't checked myself.
> > > https://invent.kde.org/plasma/plasma-workspace/-/blob/master/kioworkers/
> > > desktop/desktopnotifier.cpp
> > > 
> > > Another to check is to launch `kcmshell6 kcm_kded` and whether or not
> > > "Directory Watcher" is launched/running.
> > 
> > Why should folder or desktop view affect the behaviour of a file manager's
> > ability to monitor its own trash? 
> 
> Because dolphin is mostly tested/used in plasma with default settings, this
> hasn't been noticed.
> 
> KDE code spans decades, that we inherit as-is by from previous maintainers,
> that had limited resources as do we always.
> Code evolves organically often without overarching design, this is
> especially true for old components such as trash:/.
> 
> > A file manager should be entirely independant of a user's desktop settings.
> 
> You are correct dolphin shouldn't depend on this, not primarly for design
> but for not-plasma users of dolphin. Fixing this might be a fix for this bug.
> 
> But please answer to my questions so I actually _know_ that's the issue.
> That would be more valuable to fix the bug than having to explain the past.

Understood. But I just tested Dolphin in both folder and desktop view and the
results are the same for both. Emtpy trash continues to show contents until
refreshed manually.

-- 
You are receiving this mail because:
You are on the CC list for the bug.