diff options
Diffstat (limited to 'ChangeLog')
| -rw-r--r-- | ChangeLog | 16 |
1 files changed, 8 insertions, 8 deletions
@@ -22703,7 +22703,7 @@ v0.9.1-beta1 - 11-Feb-2007 Disable the use of the DImg raw loader when loading as DImg from digikamthumbnail ioslave. - We are using KProcess for the raw loader and make two + We are using TDEProcess for the raw loader and make two assumptions: - there is an event loop (not for ioslaves) - the loader is not called from the event loop thread (currently @@ -22711,7 +22711,7 @@ v0.9.1-beta1 - 11-Feb-2007 The DImg raw loader is not needed - DcrawIface is called before. So the problem of the loader entering an endless loop (because no - events from KProcess + events from TDEProcess are delivered) arises only if a file is identified as RAW, but dcraw does not support it. @@ -32079,10 +32079,10 @@ v0.9.0-beta1 - 20/07/2006 the app is closed while a raw image is being loaded in the histogram side bar. - The KProcess-based raw loader is waiting for the dcraw process + The TDEProcess-based raw loader is waiting for the dcraw process to finish, but the main thread is wait()ing for the thread to finish, - and no KProcess events are delivered. + and no TDEProcess events are delivered. This hack can be removed when we port to Qt4 and use the synchronous QProcess. @@ -35473,7 +35473,7 @@ v0.9.0-beta1 - 20/07/2006 - Fix broken loading with dcraw and all parameter witch require a value. - Since we use KProcess, implementation need to use QString at + Since we use TDEProcess, implementation need to use QString at all, especially to add space between option and value. The better way is to use QString::arg() method. - Add comments about dcraw Quality rules with digiKam. @@ -35512,12 +35512,12 @@ v0.9.0-beta1 - 20/07/2006 * trunk/extragear/graphics/digikam/libs/dimg/loaders/rawloader.cpp, trunk/extragear/graphics/digikam/libs/dimg/loaders/rawloader.h: digikam from trunk: - Use KProcess for RAW image loader. + Use TDEProcess for RAW image loader. Loading can now be cleanly aborted. - This is a good example that KProcess is not the perfect tool for + This is a good example that TDEProcess is not the perfect tool for use - with our shiny new multithreaded loader because KProcess is not + with our shiny new multithreaded loader because TDEProcess is not reentrant, but there are more advantages (wraps all system programming) so that |