From kde-core-devel Mon Aug 13 11:35:58 2007 From: Hans Meine Date: Mon, 13 Aug 2007 11:35:58 +0000 To: kde-core-devel Subject: Konqueror internals question (hunting an annoying KDE3 usability Message-Id: <200708131336.05465.hans_meine () gmx ! net> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=118700497825707 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart1443943.ck3YZxIUgI" --nextPart1443943.ck3YZxIUgI Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi! I was just trying to find out why Ctrl-N (new tab) clears the location bar= =20 twice. This annoys me a lot, since I always start typing=20 e.g. "gg:konqueror rules", but end up with "ror rules" in the=20 location bar (especially in high-load situations). I found out that the=20 guilty KonqMainWindow::slotPartActivated() gets called twice when opening a= =20 new tab (both calls via KonqViewManager::emitActivePartChanged()), which=20 looks like a bug AFAICS. The reason is that KonqViewManager::showTab() 1) first calls showPage(), which leads to a call of setActivePart() that=20 starts m_activePartChangedTimer, and then 2) directly calls emitActivePartChanged(). 3) Then the timer from 1) fires and emitActivePartChanged() is called again. What I did not yet find out is why showPage() leads to a call of=20 setActivePart() (although that does not sound wrong in any way). Now maybe= =20 someone with more knowledge of Konquerors internals could comment on this=20 (and the above)? Ciao, / / .o. /--/ ..o / / ANS ooo --nextPart1443943.ck3YZxIUgI Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQBGwEIfJ8iuK6bBAPMRAlr+AKCeWZuH5PDVa/PttwHukOcwj3P2nQCgmUYY WEeL+R9+/zHgyabfvMYKrVQ= =e/aV -----END PGP SIGNATURE----- --nextPart1443943.ck3YZxIUgI--