Version: 2.6.1 (using KDE KDE 3.5.1) Installed from: SuSE RPMs OS: Linux Ark 2.5.2 (KDE 3.4.2 under SUSE Linux 10.0) had a list view style interface. Ark 2.6.1 (KDE 3.5.1) uses a nested tree view. I wish there was an option to use the older Ark's view, as it was much more useful to me. I prefer to see the files, not just upper-level folders. The search function is much less useful in the new view, since the results only display the upper-level folders that contain files that match the search criteria, forcing the user to open each successive folder to get down to the actual files. There isn't even an "expand all" function. Please add an option for the "classic view" or whatever you want to call it.
Here on my KDE-3.5.6, ark opens all folders in the tree when I open an archive. So you can see all files in all levels, and also the filter field then acts on all entries in the archive. Is that what you want ?
I see the same thing in the version of ark I'm using now. One of the recent patches I applied must have changed the behavior. This is a much better view, and the search now shows the files, not just upper-level folders. However, it's not possible to sort the view on file name, regardless of folder. I would like to be able to do that too. If ark had the option to enable the behavior it used to have, it would be much more useful to me. Currently I have to use fileroller from gnome for some tasks that ark used to be fine for.
This might even be done using dolphin components
I'm not sure what this issue is about. Ark 2.12 seems to list contents in details view, but it still forces folders to be displayed as such, not providing a list of all files in the archive (which is what I'd like) regardless of folders.
*** Bug 236694 has been marked as a duplicate of this bug. ***
Changing the default assignee in the currently open Ark bug reports to me.
*** Bug 342693 has been marked as a duplicate of this bug. ***
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.