You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
f7e71d4771
This will also compile with TQt for Qt3, and should not cause any problems with dependent modules such as kdebase. If it does then it needs to be fixed! git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdelibs@1214149 283d02a7-25f6-0310-bc7c-ecb5cbfe19da |
14 years ago | |
|---|---|---|
| .. | ||
| CMakeLists.txt | 14 years ago | |
| Makefile.am | 15 years ago | |
| README | 15 years ago | |
| main.cpp | 14 years ago | |
| main.h | 14 years ago | |
README
kfmexec is launched when the user wants to open a remote file with an application that only supports local files. For this it does the following: - downloads a remote file to a temp location - starts a 'local' application with that temp file as argument - wait fors application to be exited - if the modification time of the file is different from the original one, (because the file was modified) then it offers re-uploading the modified version. This is how you offer network transparency to apps that don't have it. BUT: with KUniqueApplication, this breaks, because the app returns at once, so we have no way to know when the user finished editing the file... Conclusion: if the application has network transparency built-in, it should put "%u" in its desktop file - and kfmexec isn't used -. If it doesn't, either it's a KApplication and kfmexec does its job, or it's a KUniqueApplication and... kfmexec can't see modifications to the file. Be warned. From Waldo: "The program doesn't return _at once_. It returns after "newInstance()" returns. So if you open the file there it will still work. (Or rename it)" David Faure <faure@kde.org> 20-May-2000