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

List:       kde-kimageshop
Subject:    Re: Showstopper tablet bug for Krita 1.5
From:       Adrian Page <adrian () pagenet ! plus ! com>
Date:       2006-03-25 17:14:04
Message-ID: 44257A5C.6040304 () pagenet ! plus ! com
[Download RAW message or body]

Bart Coppens wrote:
> On Saturday 25 March 2006 17:17, Bart Coppens wrote:
>> Reproduceable (approximately 1.5-rc1 code, but still trunk) as follows:
>> Start krita. Select the Text tool (to add text on a layer). Click _with the
>> tablet_ on the layer. Watch how krita first spawns LOTS of popups for the
>> text, and then with that makes it unable to do anything in your current X
>> session, basically.
> Aha, this might be be a (bad? :P) clue to those knowledgeable enough of tablet 
> code:
> So I wanted to get a backtrace of the hanging Krita. I ran it in a gdb, with 
> the intention of then killing it remotely, and getting a backtrace in the 
> process. But, if I ran it in gdb, it just spawned a LOT of dialogs (one time 
> 13, another time 40 or so), but didn't hang. My suspicion was that Qt 
> automatically does -nograb when being run in gdb, but -dograb seemed to make 
> no difference. So I'm no step further, but maybe someone else gets an insight 
> with this?

I can reproduce this. When the text input dialog enters its event loop, 
X seems to be sending the button release event again, causing the dialog 
to be displayed again, and so on... I'll look into why this is happening.

Adrian

_______________________________________________
kimageshop mailing list
kimageshop@kde.org
https://mail.kde.org/mailman/listinfo/kimageshop
[prev in list] [next in list] [prev in thread] [next in thread]