On Thursday 08 October 2009 00:13:48 Ronny Scholz wrote: > Recently I introduced the possibility to open a new tab via double click on > the tabbar. This was just about connecting the newTabRequest() signal to > the newTab() slot. There is a strange issue I've discovered now. > > If the double click is done inside the region where the new tab will be > shown, rekonq crashes. Pano was so kind and provided me a backtrace, which > I have attached to this mail. > It seems like the tabbar is immediately trying to move the added tab and > crashes. This may be caused by faulty mouse management, but perfectly > explains why the bug appears only if the mouse is under the new tab to be > created. If the movable property of the tabbar is set to false, the bug > disappears. > > However, aurora also has movable tabs but does not have this issue. Either > the bug lies in the internal workings of our code, or in the usage of KDE > instead of plain Qt. Unfortunately, I was not able step into this issue > deeply enough > > :( > I'm double clicking really "near" the new tab page, to be sure I'm in the place where the new tab will appear, but I cannot reproduce this issue :(
It definitely works here. rekonq 0.2.64 Qt 4.5.3 KDE 4.3.2 -- Andrea Diamantini, adjam GPG Fingerprint: 57DE 8E32 7D1A 0E16 AA52 59D8 84F9 3ECD DBF9 730F rekonq project WEB: http://rekonq.sourceforge.net IRC: rek...@freenode _______________________________________________ rekonq mailing list [email protected] https://mail.kde.org/mailman/listinfo/rekonq
