[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: KDirWatch bug and the analysis. Help is welcome!
From:       Frank Reininghaus <frank78ac () googlemail ! com>
Date:       2013-08-01 14:05:01
Message-ID: CAFoZWWgQHDLZ8qb6ASVJKqe0MswJ7WgL6G7EWHXVX1SaagRz9w () mail ! gmail ! com
[Download RAW message or body]

Hi,

2013/8/1 Thomas Lübking:
> On Donnerstag, 1. August 2013 13:24:19 CEST, Frank Reininghaus wrote:
>>
>> Hi,
>>
>> 2013/8/1 Thomas Lübking:
>>>
>>> On Donnerstag, 1. August 2013 12:44:57 CEST, Frank Reininghaus wrote: ...
>>
>>
>> Peter changed that quite some time ago already because the
>> KUniqueApplication thing caused quite a few problems (like modal
>> dialogs blocking all Dolphin windows, for example).
>
>
> At least for the example: QWidget::setWindowModality(Qt::WindowModal);

OK, thanks for the hint! Not all modal dialogs come from Dolphin
itself though (example: KIO's "File exists already" dialog), so one
would have to make sure that these external dialogs use
Qt::WindowModal too.

> Is there a more exhaustive list of KUA blocker bugs?

Here is the commit:

http://quickgit.kde.org/?p=kde-baseapps.git&a=commit&h=fff7573ebb910712ad97951bf1762e6a7bb0bdc7

It also mentions that the "each window in its own process" approach
prevents that a crash brings down all Dolphin windows. This is still
true, of course, but the times when Dolphin crashed a lot because of
bugs in Strigi and Nepomuk are over thanks to Vishehs's awesome work
:-)

> (If there's at all interest to have it that way again)

Well, if it can be done without regressions (except for the "one
window crashes all" issue), then I wouldn't mind. It would reduce the
memory usage and the startup time, after all.

Cheers,
Frank
[prev in list] [next in list] [prev in thread] [next in thread]