Version: (using KDE 4.3.4) OS: Linux Installed from: Slackware Packages I use Slackware, and I have the both -current and -stable on my machine. So I use KDE 4.2.4 and also use KDE 4.3.4 sometimes. In KDE 4.2.4 dolphin always remembers the view properties of every place, even remote places (through samba). But in KDE 4.3.4 that don't happens. In folders that are in remote places, dolphin use always the same settings. It don't remembers the view settings of that places. Any one notice this? It is a bug?
Thanks for the report, but I cannot reproduce the issue. It might be related to the samba protocol... Do you work on the same samba share with both KDE versions? Do you have write permissions? For non-local directories Dolphin remembers the view properties locally inside ~/.kde4/share/apps/dolphin/view_properties - could you check whether there is a folder inside that is not called "global"?
In ~/.kde/share/apps/dolphin/view_properties there is a folder called "global" and another called "local" I have two users, one for kde 4.3.4 and another to 4.2.4 to use them in slackware-current and slackware-stable. In ~/.kde/share/apps/dolphin/view_properties of user of 4.2.4 there is a folder called "remote".
I use the same samba share with both KDE versions. I have also write permissions on both KDE versions. In KDE 4.3.4 at ~/.kde/share/apps/dolphin/view_properties I have a folder called "local" and another called "global". In KDE 4.2.4 at ~/.kde/share/apps/dolphin/view_properties I have a folder called "remote" where I think that dolphin view properties of my samba shares are stored.
I would like that in a future release of KDE, that old behavior be back. Is nice that dolphin "remembers" the view properties of folders in samba shares.
I'll set the status of this wish to CONFIRMED, as we have all the needed information.
I'm sorry, but may I clear things up? Why in hell is this a wish? Dolphin has a setting to remember view properties for each folder and this setting IS NOT working in some circumstances. I may be wrong, but to me it's a definitive bug.