Bug 90980

Version:            (using KDE KDE 3.3.0)
Compiler:          gcc 3.3.4 
OS:                Linux

Most kioslaves (e.g. zip) seem to work in such a way, that when e.g. zip:/some-file.zip is open in konqueror and some file X's icon is clicked, that file is extracted to a temporary file in /tmp (suppose it is called /tmp/Y). Now, this is OK for most applications, but some applications (e.g. kuickshow) have a 'browsing' mode - viewing many files from a single directory one after another. However, with the kioslave mechanism described above, this doesn't work as expected. If I click on zip:/some-file.zip/X and open it with kuickshow this way, kuickshow is really opening /tmp/Y (that is, /tmp/Y is put on kuickshow's command line). Thus, if PgDown is pressed in kuickshow, the next file in /tmp is opened (provided it exists), not the next file in some-file.zip.
Optimally, KDE apps could accept kioslave:/ URIs on the command line (and implement a correct definition of what 'next file in current dir' is for arbitrary kioslaves) and konqueror could somehow 'know' whether an app accepts such parameters or not, so that e.g. opening X.png from a zip file would result in running 'kuickshow zip:/some-file.zip/X.png' if kuickshow was selected for handling the file and if e.g. GIMP was used, the command line would be 'gimp /tmp/temp-file-Y.png'. I am afraid, however, that this would be hard to implement.